Triple
T36743938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paekākāriki |
E907699
|
entity |
| Predicate | hasNearbyWalkingTrack |
P12052
|
FINISHED |
| Object | Paekākāriki Escarpment Track |
—
|
NE NERFINISHED |
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: Paekākāriki Escarpment Track | Statement: [Paekākāriki, hasNearbyWalkingTrack, Paekākāriki Escarpment Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWalkingTrack Context triple: [Paekākāriki, hasNearbyWalkingTrack, Paekākāriki Escarpment Track]
-
A.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
B.
hasNearbyTrail
chosen
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
D.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
E.
hasNearbyRacetrack
Indicates that one entity is located close to or in the vicinity of a racetrack.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:12 p.m.