Triple
T18010792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cakaudrove |
E430871
|
entity |
| Predicate | hasTraditionalChieflySystem |
P120851
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cakaudrove, hasTraditionalChieflySystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalChieflySystem Context triple: [Cakaudrove, hasTraditionalChieflySystem, true]
-
A.
hasTraditionalRulers
Indicates that one entity possesses or is governed by traditional rulers associated with it.
-
B.
hasTraditionalCapital
Indicates that an entity serves or is recognized as the traditional or historical capital of another entity.
-
C.
hasTraditionalInstitutions
Indicates that an entity possesses or is associated with long-established, customary social, cultural, or governance institutions.
-
D.
hasChieftaincyStructure
chosen
Indicates that an entity possesses an organized system of traditional leadership or chieftaincy hierarchy.
-
E.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51fc108819089e6c130a89811bc |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.