Triple
T2426195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahiya Sottaiev |
E53531
|
entity |
| Predicate | mountElbrusElevationApprox |
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: [Ahiya Sottaiev, mountElbrusElevationApprox, 5642 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountElbrusElevationApprox Context triple: [Ahiya Sottaiev, mountElbrusElevationApprox, 5642 metres]
-
A.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
B.
includesHighestMountainOnEarth
Indicates that the subject entity contains or encompasses the location of the tallest mountain on Earth.
-
C.
summitElevation
chosen
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
D.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
E.
averageSummitTemperature
Indicates the typical or mean temperature measured at the summit of a location over a defined period.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.