Triple
T5491118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chachani |
E123701
|
entity |
| Predicate | isClimbedWithoutTechnicalGear |
P64415
|
FINISHED |
| Object | yes in normal dry-season route |
—
|
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: yes in normal dry-season route | Statement: [Chachani, isClimbedWithoutTechnicalGear, yes in normal dry-season route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbedWithoutTechnicalGear Context triple: [Chachani, isClimbedWithoutTechnicalGear, yes in normal dry-season route]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
C.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
D.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
E.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927f198c8190889b555be9bf9765 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd925c62a88190ac932444d5170bdd |
completed | March 20, 2026, 6:30 p.m. |
Created at: March 20, 2026, 2:10 p.m.