Triple
T29415177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazama rufina |
E746005
|
entity |
| Predicate | foundInElevationRange |
P1977
|
FINISHED |
| Object | 1400–3500 m 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: 1400–3500 m above sea level | Statement: [Mazama rufina, foundInElevationRange, 1400–3500 m above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInElevationRange Context triple: [Mazama rufina, foundInElevationRange, 1400–3500 m above sea level]
-
A.
foundInElevation
Indicates that something exists, occurs, or is located at a particular elevation or height above a reference level.
-
B.
typicalElevationRange
chosen
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
C.
tracksAltitudeRange
Indicates that something monitors or records the minimum and maximum altitude values over a given period or area.
-
D.
elevationCoverageApproximate
Indicates an approximate or estimated representation of how elevation values are covered or distributed over a given area or dataset.
-
E.
elevationMinApprox
Indicates an approximate value for the minimum elevation associated with an entity or location.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 3 p.m.