Triple
T38462588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Asian empires |
E912488
|
entity |
| Predicate | originOfRulingElites |
P57282
|
FINISHED |
| Object | Turkic |
—
|
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: Turkic | Statement: [Central Asian empires, originOfRulingElites, Turkic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfRulingElites Context triple: [Central Asian empires, originOfRulingElites, Turkic]
-
A.
aristocraticOrigin
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
-
B.
rulingClassBackground
Indicates that an entity comes from, or is associated with, a socially or politically dominant (ruling) class background.
-
C.
hadRulingClass
Indicates that a particular group or class held dominant political, economic, or social power over a society or entity.
-
D.
ethnicGroupOfRulers
chosen
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
E.
primaryEthnicElite
Indicates that the subject belongs to the main or dominant ethnic group that holds primary political, economic, or social power within a society or institution.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.