Triple
T20973143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson station |
E516552
|
entity |
| Predicate | hasStationHouseType |
P142313
|
FINISHED |
| Object | elevated station house |
—
|
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: elevated station house | Statement: [Wilson station, hasStationHouseType, elevated station house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationHouseType Context triple: [Wilson station, hasStationHouseType, elevated station house]
-
A.
hasStationHouseLocation
Indicates that a station house is located at or associated with a specific place or geographic location.
-
B.
isStationHouseOf
Indicates that a particular station building or facility serves as the designated station house for a given station or transit stop.
-
C.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
D.
hasStationBuilding
Indicates that a station is associated with or includes a station building as part of its facilities.
-
E.
hasStationHall
Indicates that one entity (typically a station) includes or is associated with a station hall area as part of its structure or facilities.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba2406c8190bd75dec585c14bfa |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:45 p.m.