Triple
T9832880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto gauge |
E239029
|
entity |
| Predicate | usedOnLineType |
P14437
|
FINISHED |
| Object | heavy-rail subway |
—
|
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: heavy-rail subway | Statement: [Toronto gauge, usedOnLineType, heavy-rail subway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnLineType Context triple: [Toronto gauge, usedOnLineType, heavy-rail subway]
-
A.
alsoUsedOnLine
Indicates that something used in one context, medium, or location is additionally used on a specific line (such as a route, circuit, or sequence).
-
B.
operatesOnLine
Indicates that an entity conducts operations, services, or activities along a specific line or route.
-
C.
lineUses
chosen
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
-
D.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
E.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb336bfc4819084f0d4d6d1867484 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.