Triple
T17288344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral Cove |
E419715
|
entity |
| Predicate | walkingTrackApproxDuration |
P53938
|
FINISHED |
| Object | 30–45 minutes one way |
—
|
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 one way | Statement: [Cathedral Cove, walkingTrackApproxDuration, 30–45 minutes one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkingTrackApproxDuration Context triple: [Cathedral Cove, walkingTrackApproxDuration, 30–45 minutes one way]
-
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.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
D.
showRouteDuration
Indicates that an entity displays or provides the duration required to traverse a specific route.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43781b7808190a0528ee9c54a0c66 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.