Triple
T29304033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changamire |
E743039
|
entity |
| Predicate | seatOfPowerType |
P166824
|
FINISHED |
| Object | hilltop capitals |
—
|
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: hilltop capitals | Statement: [Changamire, seatOfPowerType, hilltop capitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatOfPowerType Context triple: [Changamire, seatOfPowerType, hilltop capitals]
-
A.
typeOfOffice
Indicates the specific category or kind of office that an office entity belongs to (e.g., executive, legislative, judicial, or other office types).
-
B.
typeOfGovernmentHead
Indicates the specific role or office that serves as the head of a given system of government.
-
C.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
D.
typeOfHeadOfGovernmentBody
Indicates the specific kind or category of governing body for which an entity serves as the head of government.
-
E.
governingPowerRelationship
Indicates a relationship where one entity holds authoritative control, influence, or ruling power over another entity.
- F. None of above. chosen
Provenance (4 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a5724c8190b3c31ea61745a426 |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:11 p.m.