Triple
T14381421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadavu Province |
E356610
|
entity |
| Predicate | hasTraditionalStructure |
P72652
|
FINISHED |
| Object | chiefly system |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: chiefly system | Statement: [Kadavu Province, hasTraditionalStructure, chiefly system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalStructure Context triple: [Kadavu Province, hasTraditionalStructure, chiefly system]
-
A.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
B.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
-
C.
traditionalStructure
chosen
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900bbfb08190a1e56f281a2374c0 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.