Triple
T25398195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumding railway division |
E636347
|
entity |
| Predicate | gaugeTypeManaged |
P39342
|
FINISHED |
| Object | meter gauge (historical) |
—
|
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 (historical) | Statement: [Lumding railway division, gaugeTypeManaged, meter gauge (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeTypeManaged Context triple: [Lumding railway division, gaugeTypeManaged, meter gauge (historical)]
-
A.
gaugeType
chosen
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
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.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
D.
gaugeValue
Indicates the measured or current reading associated with a particular gauge or measurement instrument.
-
E.
gaugeClass
Indicates that one entity is classified as a particular type or category of gauge.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:50 p.m.