Triple
T11755056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuliʻouʻou Ridge Trail |
E279501
|
entity |
| Predicate | isOutAndBack |
P101187
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kuliʻouʻou Ridge Trail, isOutAndBack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOutAndBack Context triple: [Kuliʻouʻou Ridge Trail, isOutAndBack, true]
-
A.
isOneWay
Indicates that the relationship or action proceeds in only one direction from a source entity to a target entity, without a corresponding reverse relation.
-
B.
isRailTrail
Indicates that a path or route is a rail trail, meaning it follows or repurposes a former or existing railway corridor for recreational or transportation use.
-
C.
hasRecreationalRoute
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
D.
hasTowpath
Indicates that a waterway or canal is accompanied by a path running alongside it, typically used for towing boats.
-
E.
hasSwitchbacks
Indicates that a path, road, or trail includes sharp, back-and-forth turns (zigzags) used to navigate steep terrain.
- F. None of above. chosen
Provenance (4 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.