Triple
T33121021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sierra Bermeja |
E847594
|
entity |
| Predicate | vegetationAdaptedTo |
P130825
|
FINISHED |
| Object | ultramafic soils |
—
|
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: ultramafic soils | Statement: [Sierra Bermeja, vegetationAdaptedTo, ultramafic soils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vegetationAdaptedTo Context triple: [Sierra Bermeja, vegetationAdaptedTo, ultramafic soils]
-
A.
typicalVegetationAdaptation
chosen
Indicates the characteristic ways in which vegetation is adapted to the prevailing environmental conditions of a given area.
-
B.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
C.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
D.
vegetationStructure
Indicates the structural characteristics or arrangement of plant life in an area, such as its layering, density, or complexity.
-
E.
hasVegetationRole
Indicates that an entity participates in or is assigned a specific functional role related to vegetation (such as growth, maintenance, or impact on plant life).
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d718e52c81908e158907db3ec765 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.