Triple
T18720523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis station (Purple Line) |
E457760
|
entity |
| Predicate | hasPedestrianUnderpassOrOverpass |
P24311
|
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: [Davis station (Purple Line), hasPedestrianUnderpassOrOverpass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianUnderpassOrOverpass Context triple: [Davis station (Purple Line), hasPedestrianUnderpassOrOverpass, yes]
-
A.
hasUnderpass
chosen
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
B.
hasPedestrianOverpass
Indicates that there exists a pedestrian overpass connecting or spanning parts of the referenced location or infrastructure.
-
C.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
D.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasAnimalOverpasses
Indicates that designated overpass structures exist to allow animals to safely cross over a roadway, railway, or similar barrier.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab9e0dc8190bf579d7e89e941f4 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.