Triple
T21291765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quandary Peak |
E524808
|
entity |
| Predicate | isClimbedYearRound |
P62549
|
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: [Quandary Peak, isClimbedYearRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbedYearRound Context triple: [Quandary Peak, isClimbedYearRound, true]
-
A.
isClimbedAllYear
chosen
Indicates that the subject is climbed continuously or is suitable for climbing throughout the entire year, without a specific season.
-
B.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
C.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
D.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
E.
hasClimbingHistorySince
Indicates that an entity has been engaged in climbing activities continuously or recurrently starting from a specified point in time.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736da28648190ae3f63c6ba1f6d6f |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.