Triple
T20058198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odintsovo–Golitsyno railway line |
E499395
|
entity |
| Predicate | trackGaugeStandard |
P391
|
FINISHED |
| Object | Russian 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: Russian gauge | Statement: [Odintsovo–Golitsyno railway line, trackGaugeStandard, Russian gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeStandard Context triple: [Odintsovo–Golitsyno railway line, trackGaugeStandard, Russian gauge]
-
A.
trackGauge
chosen
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
trackGaugeOptions
Indicates the available or applicable gauge (measurement) configurations that can be used for a given track.
-
C.
formerTrackGauge
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
D.
standardGaugeWidth
Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
-
E.
nonStandardGauge
Indicates that the gauge used in a railway or track segment deviates from the standard track gauge dimension.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637325908190aefc0e27e2ed5750 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.