Triple
T36576398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khan of the Uzbeks |
E902263
|
entity |
| Predicate | hasLegitimacySource |
P139669
|
FINISHED |
| Object | tribal support |
—
|
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: tribal support | Statement: [Khan of the Uzbeks, hasLegitimacySource, tribal support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegitimacySource Context triple: [Khan of the Uzbeks, hasLegitimacySource, tribal support]
-
A.
authorityLegitimacyBasis
Indicates the foundational source or justification that makes an authority’s power or right to rule recognized as valid or legitimate.
-
B.
isOfficialSourceFor
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
C.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
D.
hasSourceOfData
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
-
E.
legitimacyClaimedFrom
chosen
Indicates that an entity bases or derives its perceived legitimacy or authority from another specified source or entity.
- 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_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:11 p.m.