Triple
T5875123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Col |
E130606
|
entity |
| Predicate | climbingSeasonUsage |
P1325
|
FINISHED |
| Object | pre-monsoon (spring) |
—
|
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: pre-monsoon (spring) | Statement: [South Col, climbingSeasonUsage, pre-monsoon (spring)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingSeasonUsage Context triple: [South Col, climbingSeasonUsage, pre-monsoon (spring)]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
climbingRegulations
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
C.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
D.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
E.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.