Triple
T15956438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kot Diji Fort |
E386946
|
entity |
| Predicate | overlooks |
P1323
|
FINISHED |
| Object | Kot Diji (town) |
E78478
|
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: Kot Diji (town) | Statement: [Kot Diji Fort, overlooks, Kot Diji (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kot Diji (town) Context triple: [Kot Diji Fort, overlooks, Kot Diji (town)]
-
A.
Kot Diji
chosen
Kot Diji is an ancient archaeological and fort site in Sindh, Pakistan, known for its pre-Harappan settlement remains and well-preserved early 19th-century fort.
-
B.
Koṭa
Koṭa is a Dravidian language spoken by the indigenous Kota people in the Nilgiri Hills of southern India.
-
C.
Kazipet
Kazipet is a major railway and educational hub in the Hanamkonda/Warangal urban area of Telangana, India.
-
D.
Kotkapura
Kotkapura is a historic town and commercial center in the Faridkot district of Punjab, India, known for its textile and agricultural markets.
-
E.
Jatoi
Jatoi is a city in southern Punjab, Pakistan, known primarily as an agricultural and market center for the surrounding rural region.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156fb29848190a55cabb49cb19575 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe7c8ef081908fa6da7975c271f6 |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:53 a.m.