Triple
T11722172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp 5 (on-route bivouac ledge) |
E278663
|
entity |
| Predicate | isCheckpointFor |
P30109
|
FINISHED |
| Object | progress on multi-day Nose ascents |
—
|
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: progress on multi-day Nose ascents | Statement: [Camp 5 (on-route bivouac ledge), isCheckpointFor, progress on multi-day Nose ascents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCheckpointFor Context triple: [Camp 5 (on-route bivouac ledge), isCheckpointFor, progress on multi-day Nose ascents]
-
A.
hasCheckpoint
chosen
Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
-
B.
hasCheckpointType
Indicates that a checkpoint is associated with a specific type or category defining its role or characteristics.
-
C.
hasCheckpointControl
Indicates that one entity exercises control, management, or authority over a checkpoint associated with another entity.
-
D.
wasCheckpointName
Indicates that an entity previously had a specific checkpoint name assigned to it.
-
E.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in time.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.