Triple
T15422626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC Davisville Carhouse |
E369420
|
entity |
| Predicate | isRailFacilityType |
P63327
|
FINISHED |
| Object | carhouse |
—
|
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: carhouse | Statement: [TTC Davisville Carhouse, isRailFacilityType, carhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailFacilityType Context triple: [TTC Davisville Carhouse, isRailFacilityType, carhouse]
-
A.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
B.
isRailInfrastructure
Indicates that something functions as or is classified as part of a railway-related physical infrastructure or system.
-
C.
hasRailwayInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
D.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
E.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.