Triple
T32000258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taibugid principality |
E817105
|
entity |
| Predicate | dynasticFoundationOf |
P92833
|
FINISHED |
| Object | Siberian Khanate |
—
|
NE NERFINISHED |
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: Siberian Khanate | Statement: [Taibugid principality, dynasticFoundationOf, Siberian Khanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticFoundationOf Context triple: [Taibugid principality, dynasticFoundationOf, Siberian Khanate]
-
A.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
B.
founderDynasty
chosen
Indicates that an entity is the founding member or originator of a particular dynasty.
-
C.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
D.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
E.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fb2f48819095ee389b66f69b7c |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:14 a.m.