Triple
T15179982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boiling Pot Lookout |
E362716
|
entity |
| Predicate | trailDistanceFromNoosaHeadsCarpark |
P63487
|
FINISHED |
| Object | short walk |
—
|
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: short walk | Statement: [Boiling Pot Lookout, trailDistanceFromNoosaHeadsCarpark, short walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceFromNoosaHeadsCarpark Context triple: [Boiling Pot Lookout, trailDistanceFromNoosaHeadsCarpark, short walk]
-
A.
distanceToNoosaHeads
Indicates the spatial distance between a given location and Noosa Heads.
-
B.
distanceToNoosaHeads_km
Indicates the physical distance, measured in kilometers, between a given location and Noosa Heads.
-
C.
distanceToNarooma
Indicates the measured spatial distance between a given entity and the location Narooma.
-
D.
distanceToPerisherByRoad
Indicates the road travel distance required to reach Perisher from a given location.
-
E.
trailDistanceApprox
chosen
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00664caac81909bee1268264769f8 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.