Triple
T29214025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afro-alpine ecosystem |
E740616
|
entity |
| Predicate | ecoregionTypeOf |
P41592
|
FINISHED |
| Object | Afroalpine ecoregions |
—
|
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: Afroalpine ecoregions | Statement: [Afro-alpine ecosystem, ecoregionTypeOf, Afroalpine ecoregions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecoregionTypeOf Context triple: [Afro-alpine ecosystem, ecoregionTypeOf, Afroalpine ecoregions]
-
A.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
B.
ecoregionsInclude
Indicates that one ecoregion spatially contains or encompasses another ecoregion or area within its boundaries.
-
C.
ecoregionContext
Indicates the environmental or ecological setting within which an entity exists or an interaction occurs, defined by its surrounding ecoregion.
-
D.
naturalRegionType
chosen
Indicates the type or category of natural region to which a given area or place belongs.
-
E.
ecoregionCode
Indicates the specific ecological region identifier associated with an entity, linking it to a defined environmental or biogeographic zone.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664075b948190b10f2d87d27ea8c9 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:12 p.m.