Triple
T21698272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olyokma Nature Reserve |
E535582
|
entity |
| Predicate | floraBiome |
P952
|
FINISHED |
| Object | boreal forest |
—
|
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: boreal forest | Statement: [Olyokma Nature Reserve, floraBiome, boreal forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraBiome Context triple: [Olyokma Nature Reserve, floraBiome, boreal forest]
-
A.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
B.
biome
chosen
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
C.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
D.
studiedFloraOf
Indicates that a subject conducted research or examination on the plant life (flora) of a specified object or region.
-
E.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b7caca0819083d839b276ae015b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.