Triple
T17800968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muzaffargarh |
E444422
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | Kot Addu |
—
|
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: Kot Addu | Statement: [Muzaffargarh, roadConnection, Kot Addu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kot Addu Context triple: [Muzaffargarh, roadConnection, Kot Addu]
-
A.
Kot Addu
chosen
Kot Addu is a prominent city in Pakistan known for its strategic location in southern Punjab and its role as a regional commercial and agricultural hub.
-
B.
Kot Diji
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.
-
C.
Kumhrar
Kumhrar is an archaeological site in Patna, India, known for the excavated remains of ancient Pataliputra, the capital of the Mauryan Empire.
-
D.
Shakardara
Shakardara is a town and administrative settlement in Pakistan’s Khyber Pakhtunkhwa province, known for its role within the Kohat region.
-
E.
Khotta
Khotta is an alternate name for the Khortha language, an Indo-Aryan language spoken primarily in the Indian state of Jharkhand.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487ff42108190b82ceb4466aa2dff |
completed | April 19, 2026, 7:45 a.m. |
Created at: April 10, 2026, 10:13 a.m.