Triple
T19345417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island Gardens |
E483862
|
entity |
| Predicate | hasWalkingConnection |
P90518
|
FINISHED |
| Object | Greenwich via Greenwich Foot Tunnel |
—
|
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: Greenwich via Greenwich Foot Tunnel | Statement: [Island Gardens, hasWalkingConnection, Greenwich via Greenwich Foot Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingConnection Context triple: [Island Gardens, hasWalkingConnection, Greenwich via Greenwich Foot Tunnel]
-
A.
hasWalkingRouteConnection
chosen
Indicates that there is a walkable path or route directly connecting two locations.
-
B.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
C.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
D.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
-
E.
hasWalkwayPosition
Indicates the spatial or relative position of an entity along or within a walkway.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185a56b4819089336564959b84df |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.