Triple
T28015265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flora of the Rocky Mountains |
E707529
|
entity |
| Predicate | includesBiomeZone |
P110631
|
FINISHED |
| Object | montane zone |
—
|
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: montane zone | Statement: [Flora of the Rocky Mountains, includesBiomeZone, montane zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBiomeZone Context triple: [Flora of the Rocky Mountains, includesBiomeZone, montane zone]
-
A.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
B.
isLocatedInBiome
chosen
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
C.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
D.
biogeographicZone
Indicates the biogeographic region or ecological zone in which an entity (such as a species or habitat) naturally occurs or is distributed.
-
E.
addsBiome
Indicates that one entity introduces or associates a new biome with another entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 27, 2026, 8:06 p.m.