Triple
T16734350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denali north-side climbing routes |
E406677
|
entity |
| Predicate | haveTypicalApproachDistance |
P124438
|
FINISHED |
| Object | very long |
—
|
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: very long | Statement: [Denali north-side climbing routes, haveTypicalApproachDistance, very long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTypicalApproachDistance Context triple: [Denali north-side climbing routes, haveTypicalApproachDistance, very long]
-
A.
wentTheDistance
Indicates that an entity persisted through an entire challenge, task, or event without giving up or stopping early.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
approxDistanceToJos
Indicates that one entity is located at an approximate distance from the entity referred to as Jos.
-
D.
hasApproachSide
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
E.
wentToDistance
Indicates that an entity traveled to or reached a specified distance from a reference point.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c38c9cc8190a3220cc3684388dc |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.