Triple
T14855947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wineglass Bay Lookout |
E349349
|
entity |
| Predicate | hasApproximateWalkingTimeOneWay |
P53938
|
FINISHED |
| Object | 30–45 minutes |
—
|
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: 30–45 minutes | Statement: [Wineglass Bay Lookout, hasApproximateWalkingTimeOneWay, 30–45 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateWalkingTimeOneWay Context triple: [Wineglass Bay Lookout, hasApproximateWalkingTimeOneWay, 30–45 minutes]
-
A.
hasApproximateWalkingTimeTo
chosen
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
B.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
-
C.
approximateDrivingTime
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
D.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
E.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44458ec8190be295a95f5daab14 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.