Triple
T18836508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katni district |
E460678
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Barhi |
—
|
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: Barhi | Statement: [Katni district, hasTown, Barhi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barhi Context triple: [Katni district, hasTown, Barhi]
-
A.
Barhi
Barhi is a town in the Indian state of Jharkhand that serves as a local transport and commercial hub along a major national highway corridor.
-
B.
Jimma
Jimma is a city in southwestern Ethiopia known as a major center of coffee production and regional trade.
-
C.
Jhelumi
Jhelumi is a regional dialect of the Potohari language spoken primarily in and around the Jhelum area of Pakistan.
-
D.
Barhi town
chosen
Barhi town is a small urban settlement in India known for its proximity to an industrial area that supports local economic activity.
-
E.
Parachinar
Parachinar is a major town in northwestern Pakistan near the Afghan border, known as the administrative center of Kurram District and for its strategic and sectarian-sensitive location.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.