Triple
T19348835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagpur–Bhusawal line |
E483957
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Bhusawal |
E622764
|
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: Bhusawal | Statement: [Nagpur–Bhusawal line, endPoint, Bhusawal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhusawal Context triple: [Nagpur–Bhusawal line, endPoint, Bhusawal]
-
A.
Bhusawal
chosen
Bhusawal is a major railway and commercial city in Maharashtra, India, known for its large railway junction and banana-growing region.
-
B.
Baramati
Baramati is a town in the Pune district of Maharashtra, India, known as an agricultural and industrial hub with historical and political significance.
-
C.
Chandwad
Chandwad is a town in the Nashik district of Maharashtra, India, known for its historical temples and hill forts.
-
D.
Warora
Warora is a town in Maharashtra, India, known historically for its coal mining and industrial activities within the Chandrapur district.
-
E.
Ratlam
Ratlam is a prominent commercial city in western Madhya Pradesh, India, known for its railway junction, textile and chemical industries, and production of gold and silver jewelry.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185d54c0819081715ca13a5806b4 |
completed | April 20, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07240767548190a59f13380f4122ea |
completed | May 15, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:34 p.m.