Triple
T15489232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Ngungun |
E377134
|
entity |
| Predicate | hasApproxElevation_m |
P45909
|
FINISHED |
| Object | 253 |
—
|
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: 253 | Statement: [Mount Ngungun, hasApproxElevation_m, 253]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxElevation_m Context triple: [Mount Ngungun, hasApproxElevation_m, 253]
-
A.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
B.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
C.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
hasObservationHeightApprox
Indicates that an entity has an associated observation height whose value is known only approximately rather than as an exact measurement.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faaca588190b0397bc2e27a522a |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:48 a.m.