Triple
T18232988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Arctic protected areas |
E436591
|
entity |
| Predicate | protectsBiome |
P73332
|
FINISHED |
| Object | tundra |
—
|
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: tundra | Statement: [Russian Arctic protected areas, protectsBiome, tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsBiome Context triple: [Russian Arctic protected areas, protectsBiome, tundra]
-
A.
protectsEcosystemType
chosen
Indicates that one entity safeguards, preserves, or maintains the health and integrity of a particular type of ecosystem.
-
B.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
C.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
-
D.
biomeRestriction
Indicates that something is limited to, or only valid within, specific biome types or environmental regions.
-
E.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b414308190bc7dd8e73c0a362c |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.