Triple
T28604383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakneck Ridge station |
E724002
|
entity |
| Predicate | passengerBuildings |
P171794
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Breakneck Ridge station, passengerBuildings, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerBuildings Context triple: [Breakneck Ridge station, passengerBuildings, none]
-
A.
passengerFacility
Indicates that a facility is designated for use by passengers, such as for boarding, waiting, or related passenger services.
-
B.
passengerTerminalType
Indicates the specific kind or category of passenger terminal associated with an entity.
-
C.
architectOfPassengerTerminal
Indicates that an entity served as the architect responsible for designing a specific passenger terminal.
-
D.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
E.
transportationFacility
Indicates that one entity is a facility or location used for the transportation or transit of people or goods in relation to another entity.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 4:26 a.m.