Triple
T23165166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanakapiai Valley |
E578692
|
entity |
| Predicate | trailHazard |
P134758
|
FINISHED |
| Object | stream crossings |
—
|
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: stream crossings | Statement: [Hanakapiai Valley, trailHazard, stream crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailHazard Context triple: [Hanakapiai Valley, trailHazard, stream crossings]
-
A.
hazardEncountered
chosen
Indicates that an entity has come into contact with or been exposed to a potentially dangerous or harmful condition, object, or situation.
-
B.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
C.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
D.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
E.
terrainCapability
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.