Triple
T27024343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American terrestrial ecosystems |
E680745
|
entity |
| Predicate | includeBiome |
P41820
|
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: [North American terrestrial ecosystems, includeBiome, tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeBiome Context triple: [North American terrestrial ecosystems, includeBiome, tundra]
-
A.
biomeIncludes
chosen
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
B.
addsBiome
Indicates that one entity introduces or associates a new biome with another entity.
-
C.
hasSecondaryBiome
Indicates that an entity is associated with an additional, subordinate biome type beyond its primary biome.
-
D.
isLocatedInBiome
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
E.
biome
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 27, 2026, 7:10 a.m.