Triple
T30603639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qandil Mountains |
E778976
|
entity |
| Predicate | highestPeaksElevation |
P14507
|
FINISHED |
| Object | around 3500 metres |
—
|
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: around 3500 metres | Statement: [Qandil Mountains, highestPeaksElevation, around 3500 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPeaksElevation Context triple: [Qandil Mountains, highestPeaksElevation, around 3500 metres]
-
A.
highestPeaksLocatedIn
Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
-
B.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
C.
hasHighestElevationsOf
Indicates that one entity possesses the greatest elevation values (e.g., altitudes or heights) compared to another entity or set of entities.
-
D.
summitElevation
chosen
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
E.
mountainHeight
Indicates the vertical elevation or height of a mountain, typically measured from sea level.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:25 p.m.