Triple
T121998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAX Red Line |
E2466
|
entity |
| Predicate | usesRailGauge |
P5070
|
FINISHED |
| Object | standard 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: standard gauge | Statement: [MAX Red Line, usesRailGauge, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRailGauge Context triple: [MAX Red Line, usesRailGauge, standard gauge]
-
A.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
B.
railroadEngineeringFeature
Indicates a feature, element, or characteristic specifically related to the design, construction, or operation of railroad engineering systems.
-
C.
hasRailTrail
Indicates that one location or entity possesses, includes, or is connected by a rail trail (a recreational trail converted from or running along a former or existing railway corridor) to another location or entity.
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
- F. None of above. chosen
Provenance (4 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a25739ef28819093f3f0e6bb670201 |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256c72f6c81909b619b90d829d86e |
completed | Feb. 28, 2026, 2:45 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.