Triple
T28059601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dizin |
E709065
|
entity |
| Predicate | altitudeTop |
P99098
|
FINISHED |
| Object | about 3600 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 3600 meters above sea level | Statement: [Dizin, altitudeTop, about 3600 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeTop Context triple: [Dizin, altitudeTop, about 3600 meters above sea level]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestCampAltitudeMetres
Indicates the maximum altitude in meters reached by any camp associated with the entity.
-
C.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
D.
peakElevationMetres
chosen
Indicates the maximum height of an entity above sea level, measured in metres.
-
E.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64015c504819097bb0e243a753088 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:38 p.m.