Triple
T35159951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Cape Bay |
E1015237
|
entity |
| Predicate | hasApproxWalkingTimeFromCockleCreek |
P53938
|
FINISHED |
| Object | 3 to 4 hours 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: 3 to 4 hours one way | Statement: [South Cape Bay, hasApproxWalkingTimeFromCockleCreek, 3 to 4 hours one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxWalkingTimeFromCockleCreek Context triple: [South Cape Bay, hasApproxWalkingTimeFromCockleCreek, 3 to 4 hours 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.
hasApproximateRoundTripDistanceFromMaroonLake
Indicates that an entity has an approximate total round-trip distance measured from Maroon Lake.
-
C.
isOnGreatWalk
Indicates that one location or path lies along or is part of a designated “Great Walk” route.
-
D.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
E.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:02 p.m.