Triple
T8852933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canyon Overlook Trail |
E210679
|
entity |
| Predicate | hasHazards |
P63246
|
FINISHED |
| Object | steep drop-offs |
—
|
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: steep drop-offs | Statement: [Canyon Overlook Trail, hasHazards, steep drop-offs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHazards Context triple: [Canyon Overlook Trail, hasHazards, steep drop-offs]
-
A.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
B.
hasObjectiveHazards
chosen
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
C.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
D.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
E.
hasNavigationHazard
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c55e348190957b3bbb7397e380 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.