Triple
T19794145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabalpur–Nainpur–Gondia route |
E475494
|
entity |
| Predicate | formerGauge |
P120346
|
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: [Jabalpur–Nainpur–Gondia route, formerGauge, narrow gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGauge Context triple: [Jabalpur–Nainpur–Gondia route, formerGauge, narrow gauge]
-
A.
formerTrackGauge
chosen
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
B.
historicalGauge
Indicates that one entity serves as a gauge, measure, or reference point for understanding the historical state, level, or condition of another entity.
-
C.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
D.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
E.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
- F. None of above.
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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c5a7d48190b2a384f768d13750 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.