Triple
T9300345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normal Route on Aconcagua |
E223742
|
entity |
| Predicate | technicalEquipmentSometimesRequired |
P16207
|
FINISHED |
| Object | crampons |
—
|
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: crampons | Statement: [Normal Route on Aconcagua, technicalEquipmentSometimesRequired, crampons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalEquipmentSometimesRequired Context triple: [Normal Route on Aconcagua, technicalEquipmentSometimesRequired, crampons]
-
A.
requiresDevice
chosen
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
B.
unitRequirement
Indicates that one entity specifies a required quantity or unit that another entity must meet or conform to.
-
C.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
D.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
E.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
- 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.