Triple
T11399127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Karakoram expedition of 1954 |
E270059
|
entity |
| Predicate | usedHighAltitudePorters |
P99101
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Italian Karakoram expedition of 1954, usedHighAltitudePorters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHighAltitudePorters Context triple: [Italian Karakoram expedition of 1954, usedHighAltitudePorters, true]
-
A.
usedHighAltitudePortersFrom
Indicates that an entity employed high-altitude porters originating from a specified place or group.
-
B.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
C.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
D.
hasPeakOver3000m
Indicates that the related geographic feature has at least one peak whose elevation exceeds 3000 meters above sea level.
-
E.
pilgrimageAltitudeHighPoint
Indicates the highest altitude reached along a pilgrimage route or during a pilgrimage journey.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001adc188190ae45227856156412 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.