Triple
T25532842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-thousanders of the Caucasus |
E639968
|
entity |
| Predicate | highestMemberElevation |
P14507
|
FINISHED |
| Object | 5642 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: 5642 metres | Statement: [Five-thousanders of the Caucasus, highestMemberElevation, 5642 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestMemberElevation Context triple: [Five-thousanders of the Caucasus, highestMemberElevation, 5642 metres]
-
A.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
B.
summitElevation
chosen
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
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.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 3:15 p.m.