Triple
T949677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensboro Bridge |
E20490
|
entity |
| Predicate | hasWalkway |
P18406
|
FINISHED |
| Object | pedestrian walkway |
—
|
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: pedestrian walkway | Statement: [Queensboro Bridge, hasWalkway, pedestrian walkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkway Context triple: [Queensboro Bridge, hasWalkway, pedestrian walkway]
-
A.
hasSidewalk
Indicates that a location, path, or roadway is accompanied by a designated sidewalk area for pedestrian use.
-
B.
isWalkable
Indicates that an entity can be traversed on foot, typically without obstruction or restriction.
-
C.
hasPedestrianArea
chosen
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
hasPromenade
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3c191ac819099ebf3cb32f096d8 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.