Triple
T17858664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Coochin |
E446005
|
entity |
| Predicate | hasClimbingRestriction |
P129034
|
FINISHED |
| Object | no formal climbing route, hiking only |
—
|
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: no formal climbing route, hiking only | Statement: [Mount Coochin, hasClimbingRestriction, no formal climbing route, hiking only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingRestriction Context triple: [Mount Coochin, hasClimbingRestriction, no formal climbing route, hiking only]
-
A.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
B.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
-
C.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
D.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
E.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978e68ec8190a4306f7b7bb058d7 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:17 a.m.