Triple
T32270091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC gauge |
E824391
|
entity |
| Predicate | usedOnInfrastructureType |
P2560
|
FINISHED |
| Object | streetcar tracks |
—
|
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: streetcar tracks | Statement: [TTC gauge, usedOnInfrastructureType, streetcar tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnInfrastructureType Context triple: [TTC gauge, usedOnInfrastructureType, streetcar tracks]
-
A.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
B.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
C.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
D.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69f6bc8647bc819084b1dceeb206cde5 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:42 a.m.