Triple
T32270069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC gauge |
E824391
|
entity |
| Predicate | comparedToStandardGauge |
P69893
|
FINISHED |
| Object | 1435 mm |
—
|
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: 1435 mm | Statement: [TTC gauge, comparedToStandardGauge, 1435 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparedToStandardGauge Context triple: [TTC gauge, comparedToStandardGauge, 1435 mm]
-
A.
standardGaugeWidthComparison
chosen
Indicates a comparison between the track gauge width of a railway and the standard gauge width to determine if it is equal to, narrower than, or wider than the standard.
-
B.
convertedToStandardGauge
Indicates that something previously using a different gauge has been changed or adapted to conform to a standard gauge specification.
-
C.
gaugeCompatibleWith
Indicates that one gauge can be properly used with, mounted to, or function correctly in conjunction with another specified component or system.
-
D.
nonStandardGauge
Indicates that the gauge used in a railway or track segment deviates from the standard track gauge dimension.
-
E.
gaugeConversion
Indicates a relationship where one measurement or scale is converted into another corresponding measurement or scale.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:42 a.m.