Triple
T2050698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Bridge |
E45558
|
entity |
| Predicate | hasFootpath |
P4070
|
FINISHED |
| Object | two sidewalks |
—
|
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: two sidewalks | Statement: [London Bridge, hasFootpath, two sidewalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootpath Context triple: [London Bridge, hasFootpath, two sidewalks]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
C.
hasSidewalk
chosen
Indicates that a location, path, or roadway is accompanied by a designated sidewalk area for pedestrian use.
-
D.
hasTowpath
Indicates that a waterway or canal is accompanied by a path running alongside it, typically used for towing boats.
-
E.
hasSettlementAtFoot
Indicates that a settlement is located at the base or lower slopes of a geographic feature such as a hill or mountain.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98f5f4881908d9aa0f10be44041 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.