Triple
T25624145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumba lowland forests |
E642381
|
entity |
| Predicate | elevationUpperLimit |
P80409
|
FINISHED |
| Object | approximately 1000 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: approximately 1000 meters above sea level | Statement: [Sumba lowland forests, elevationUpperLimit, approximately 1000 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationUpperLimit Context triple: [Sumba lowland forests, elevationUpperLimit, approximately 1000 meters above sea level]
-
A.
elevationRangeUpperBound
chosen
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
-
B.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
C.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
elevationThreshold
Indicates a specified elevation level at which a condition, effect, or change in state becomes applicable or is triggered.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 5:07 p.m.