Triple
T5116413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khevsureti |
E115345
|
entity |
| Predicate | hasHighestPointApprox |
P19320
|
FINISHED |
| Object | about 4000 meters above sea level |
—
|
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: about 4000 meters above sea level | Statement: [Khevsureti, hasHighestPointApprox, about 4000 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPointApprox Context triple: [Khevsureti, hasHighestPointApprox, about 4000 meters above sea level]
-
A.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
D.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
E.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cfa9f88190aa7dfd264e554899 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd7160d44081908cc64f3c14d28b81 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.