Triple
T25453325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badarpur Junction |
E637845
|
entity |
| Predicate | formerGaugeType |
P120346
|
FINISHED |
| Object | meter 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: meter gauge | Statement: [Badarpur Junction, formerGaugeType, meter gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGaugeType Context triple: [Badarpur Junction, formerGaugeType, meter gauge]
-
A.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
B.
previouslyHadGauge
Indicates that an entity had a particular gauge or measurement instrument at some time in the past, but does not necessarily have it now.
-
C.
gaugeConversion
Indicates a relationship where one measurement or scale is converted into another corresponding measurement or scale.
-
D.
formerTrackGauge
chosen
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
E.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 21, 2026, 2:03 p.m.