Triple
T36576383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khan of the Uzbeks |
E902263
|
entity |
| Predicate | isDynasticTitle |
P25666
|
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: [Khan of the Uzbeks, isDynasticTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDynasticTitle Context triple: [Khan of the Uzbeks, isDynasticTitle, true]
-
A.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
B.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
C.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
D.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
E.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.