Triple
T22601593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayan Khan |
E574833
|
entity |
| Predicate | tribalAffiliation |
P13151
|
FINISHED |
| Object | Chahar |
—
|
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: Chahar | Statement: [Dayan Khan, tribalAffiliation, Chahar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chahar Context triple: [Dayan Khan, tribalAffiliation, Chahar]
-
A.
Chahar
chosen
Chahar was a historical province and region in northern China, bordering Inner Mongolia, that became a key area of Japanese military expansion and control during the Second Sino-Japanese War.
-
B.
Quri Chay
Quri Chay is a river, known locally by this name, that flows through parts of northwestern Iran.
-
C.
Pishva
Pishva is a city in Tehran Province, Iran, known as an administrative and local commercial center for the surrounding region.
-
D.
Shahrbani
Shahrbani was the former national police force of Iran responsible for maintaining public order and security before being merged into the current Law Enforcement Command of the Islamic Republic of Iran.
-
E.
Shahgarh
Shahgarh is a town in the Sagar district of the central Indian state of Madhya Pradesh.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626db69481908ec9f9c7d320d3cb |
completed | April 29, 2026, 1:44 a.m. |
Created at: April 17, 2026, 2:50 p.m.