Triple
T531555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongols |
E12232
|
entity |
| Predicate | politicalSystemInEmpire |
P1815
|
FINISHED |
| Object | khanate |
—
|
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: khanate | Statement: [Mongols, politicalSystemInEmpire, khanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalSystemInEmpire Context triple: [Mongols, politicalSystemInEmpire, khanate]
-
A.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
B.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
C.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
-
D.
hasPolity
chosen
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
E.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.