Triple
T5925637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moe Island |
E131803
|
entity |
| Predicate | mainEcosystemType |
P964
|
FINISHED |
| Object | maritime Antarctic 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: maritime Antarctic tundra | Statement: [Moe Island, mainEcosystemType, maritime Antarctic tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEcosystemType Context triple: [Moe Island, mainEcosystemType, maritime Antarctic tundra]
-
A.
primaryEcosystem
chosen
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
B.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
C.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
D.
naturalRegionType
Indicates the type or category of natural region to which a given area or place belongs.
-
E.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.