Triple
T31073714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Everitt Park |
E791892
|
entity |
| Predicate | hasWalkingPathType |
P74037
|
FINISHED |
| Object | riverside paths |
—
|
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: riverside paths | Statement: [Nicholas Everitt Park, hasWalkingPathType, riverside paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingPathType Context triple: [Nicholas Everitt Park, hasWalkingPathType, riverside paths]
-
A.
hasWalkingRouteType
chosen
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
B.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
C.
hasWalkingPathLength
Indicates the length or distance of a designated walking path associated with an entity.
-
D.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
-
E.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 9:01 p.m.