Triple
T9300367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normal Route on Aconcagua |
E223742
|
entity |
| Predicate | peakClimbingMonths |
P1325
|
FINISHED |
| Object | December |
—
|
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: December | Statement: [Normal Route on Aconcagua, peakClimbingMonths, December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakClimbingMonths Context triple: [Normal Route on Aconcagua, peakClimbingMonths, December]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
climbingPopularity
Indicates how widely practiced, favored, or in-demand a particular form of climbing or climbing-related activity is among participants.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
climbs
Indicates that an entity moves upward onto or up the surface of another entity, typically overcoming vertical or inclined distance.
-
E.
climbDate
Indicates the date on which a particular climbing activity or ascent took place.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d070c881908bed41aada6f85ae |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.