Triple
T20353582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhindwara Junction |
E496082
|
entity |
| Predicate | previouslyHadGauge |
P139806
|
FINISHED |
| Object | narrow gauge |
—
|
LITERAL 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: narrow gauge | Statement: [Chhindwara Junction, previouslyHadGauge, narrow gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyHadGauge Context triple: [Chhindwara Junction, previouslyHadGauge, narrow gauge]
-
A.
operatedOnGauge
Indicates that an entity has performed an operation or action on a gauge, affecting its state or readings.
-
B.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
-
C.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
D.
wasPreviouslyMeasuredAs
Indicates that an entity had a specific measurement or value at an earlier time, which may differ from its current measurement.
-
E.
hasBreakOfGaugeWith
Indicates that two connected railway lines or networks meet at a point where their track gauges differ, requiring a change of trains or transfer of cargo.
- F. None of above. chosen
Provenance (4 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67851c7088190ba960a33c6dfa824 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:25 a.m.