Triple
T30767917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotuy River |
E783425
|
entity |
| Predicate | hasEcologicalZone |
P69704
|
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: [Kotuy River, hasEcologicalZone, tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcologicalZone Context triple: [Kotuy River, hasEcologicalZone, tundra]
-
A.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
B.
hasEcologicalZones
chosen
Indicates that an entity is associated with, contains, or is characterized by one or more distinct ecological zones.
-
C.
hasMajorEcoregion
Indicates that an entity is primarily located within, or chiefly associated with, a particular major ecological region.
-
D.
hasNumberOfEcoregions
Indicates the quantitative relationship specifying how many ecoregions are associated with a given entity.
-
E.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fbf3a848190a76843e839b6793f |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.