Triple
T963170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braddock Road station |
E20779
|
entity |
| Predicate | faregatesLocation |
P8430
|
FINISHED |
| Object | mezzanine |
—
|
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: mezzanine | Statement: [Braddock Road station, faregatesLocation, mezzanine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faregatesLocation Context triple: [Braddock Road station, faregatesLocation, mezzanine]
-
A.
flagshipStationLocation
Indicates the location where an organization’s primary or flagship station is situated.
-
B.
fareControlLocation
chosen
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
C.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
-
D.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b416cf4c8190bd685227db25fb53 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.