Triple
T9597080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nearctic ecozone |
E231558
|
entity |
| Predicate | hasMajorEcoregionGroup |
P26512
|
FINISHED |
| Object | Arctic Archipelago 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: Arctic Archipelago tundra | Statement: [Nearctic ecozone, hasMajorEcoregionGroup, Arctic Archipelago tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorEcoregionGroup Context triple: [Nearctic ecozone, hasMajorEcoregionGroup, Arctic Archipelago tundra]
-
A.
hasMajorEcoregion
chosen
Indicates that an entity is primarily located within, or chiefly associated with, a particular major ecological region.
-
B.
isMajorHabitatFor
Indicates that one entity serves as a primary or significant natural living environment for another entity.
-
C.
hasEcologicalZones
Indicates that an entity is associated with, contains, or is characterized by one or more distinct ecological zones.
-
D.
ecoregionCode
Indicates the specific ecological region identifier associated with an entity, linking it to a defined environmental or biogeographic zone.
-
E.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a34f5408190ba72ba8311eb259c |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.