Triple
T2393535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Duarte |
E47595
|
entity |
| Predicate | hasAverageAscentTime |
P20400
|
FINISHED |
| Object | 2–3 days |
—
|
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: 2–3 days | Statement: [Pico Duarte, hasAverageAscentTime, 2–3 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageAscentTime Context triple: [Pico Duarte, hasAverageAscentTime, 2–3 days]
-
A.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
B.
approximateAscentTimeFromRefuge
chosen
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
C.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
D.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc876d48881909e4d6f5ebe430012 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.