Triple
T16697254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taraori |
E405746
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Tarain |
E1154783
|
NE 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: Tarain | Statement: [Taraori, historicalName, Tarain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tarain Context triple: [Taraori, historicalName, Tarain]
-
A.
Tarain
chosen
Tarain is a historic town in present-day Haryana, India, best known as the site of two major 12th-century battles between the Ghurid forces and the Rajput king Prithviraj Chauhan.
-
B.
Tokhi
Tokhi is a prominent Pashtun tribe that forms part of the larger Ghilji tribal confederation in Afghanistan.
-
C.
Tajrish
Tajrish is a historic and bustling neighborhood in northern Tehran known for its traditional bazaar, central square, and proximity to the Alborz Mountains.
-
D.
Qalat
Qalat is a key urban center and provincial capital in southern Afghanistan, known for its strategic location and historical fortifications.
-
E.
Sanjar
Sanjar was a prominent 12th-century Seljuk ruler who governed the eastern provinces of the empire and is often regarded as its last great sultan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3832e93c48190a594c498e9cc901a |
completed | April 18, 2026, 1:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00919d02088190acecb1a62a100255 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.