Triple
T32570896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackay Falls |
E832509
|
entity |
| Predicate | hikingRouteHighlight |
P10970
|
FINISHED |
| Object | Milford 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: Milford Track | Statement: [Mackay Falls, hikingRouteHighlight, Milford Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikingRouteHighlight Context triple: [Mackay Falls, hikingRouteHighlight, Milford Track]
-
A.
hikingTrailPassesNear
Indicates that a hiking trail runs close to, but does not directly intersect or pass through, a specified location or feature.
-
B.
notableRouteFeature
chosen
Indicates that a route is associated with a distinctive or significant feature, such as a landmark, characteristic terrain, or other notable aspect along its path.
-
C.
notableHike
Indicates that an entity is recognized as a significant or well-known hiking route or trail.
-
D.
hikingTrailFrom
Indicates a relationship where a hiking trail originates at or departs from a specified location.
-
E.
glacialRoute
Indicates a path or course shaped, carved, or followed by a glacier as it moves across a landscape.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63aacd8819081c6c56146abeb91 |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.