Triple
T11439548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ridge of K2 |
E271104
|
entity |
| Predicate | exposureLevel |
P99309
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [North Ridge of K2, exposureLevel, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposureLevel Context triple: [North Ridge of K2, exposureLevel, very high]
-
A.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
B.
providesExposureTo
Indicates that one entity gives another entity the opportunity to be seen, noticed, or become known by a particular audience, environment, or set of influences.
-
C.
resultOfExposure
Indicates that something occurs or exists as a consequence of being exposed to a particular agent, condition, or environment.
-
D.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
E.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d800115af08190bba53dd3ff561ca1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.