Triple
T2163313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T1 subway train |
E46849
|
entity |
| Predicate | trackGaugeType |
P391
|
FINISHED |
| Object | Toronto 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: Toronto gauge | Statement: [T1 subway train, trackGaugeType, Toronto gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeType Context triple: [T1 subway train, trackGaugeType, Toronto gauge]
-
A.
trackGauge
chosen
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
C.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8d105c819098371c35c88873dc |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.