Triple
T2924191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurisilva forest |
E78803
|
entity |
| Predicate | typicalAltitudeRange |
P1977
|
FINISHED |
| Object | mid‑elevation zones |
—
|
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: mid‑elevation zones | Statement: [Laurisilva forest, typicalAltitudeRange, mid‑elevation zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAltitudeRange Context triple: [Laurisilva forest, typicalAltitudeRange, mid‑elevation zones]
-
A.
typicalElevationRange
chosen
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
typicalCamp1Altitude_m
Indicates the usual or characteristic altitude, in meters, at which the first camp in a sequence of camps is located.
-
C.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
E.
typicalCamp3Altitude_m
Indicates the usual elevation, in meters, at which the third camp in a sequence of camps is located.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.