Triple
T28588941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Polish winter Broad Peak expedition |
E723587
|
entity |
| Predicate | peakClassification |
P99117
|
FINISHED |
| Object | eight-thousander |
—
|
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: eight-thousander | Statement: [2013 Polish winter Broad Peak expedition, peakClassification, eight-thousander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakClassification Context triple: [2013 Polish winter Broad Peak expedition, peakClassification, eight-thousander]
-
A.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
B.
peakCategory
chosen
Indicates the classification or type of peak an entity belongs to, such as its rank, prominence, or categorical grouping among peaks.
-
C.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
D.
peakProminencePeriod
Indicates the time period during which something reached its highest level of prominence or significance.
-
E.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:19 a.m.