Triple
T22089987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duboce and Church |
E545886
|
entity |
| Predicate | hasCrosswalkAccess |
P78164
|
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: [Duboce and Church, hasCrosswalkAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrosswalkAccess Context triple: [Duboce and Church, hasCrosswalkAccess, yes]
-
A.
hasCrosswalks
chosen
Indicates that designated pedestrian crosswalks are present at or associated with the specified location or roadway segment.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasAccessRoadsTo
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
D.
hasTransportationCrossings
Indicates that one location or route includes points where transportation paths (such as roads, railways, or walkways) intersect or cross over/under another feature.
-
E.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e53dfc81909858cdad8b09c5fb |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.