Triple
T4047948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transbay Tube |
E84112
|
entity |
| Predicate | hasEmergencyWalkway |
P53800
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Transbay Tube, hasEmergencyWalkway, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyWalkway Context triple: [Transbay Tube, hasEmergencyWalkway, yes]
-
A.
hasEmergencyExits
Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
-
B.
hasEmergencyStairwells
Indicates that an entity is equipped with one or more stairwells specifically designated and constructed for use during emergencies.
-
C.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
-
D.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
E.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.