Triple
T32663556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Амгунь |
E835092
|
entity |
| Predicate | экосистема |
P948
|
FINISHED |
| Object | таёжная зона Дальнего Востока |
—
|
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: таёжная зона Дальнего Востока | Statement: [Амгунь, экосистема, таёжная зона Дальнего Востока]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: экосистема Context triple: [Амгунь, экосистема, таёжная зона Дальнего Востока]
-
A.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
B.
ecosystemTerm
Indicates that one entity is a term, label, or concept used within the context of an ecosystem or ecological system.
-
C.
ecosystemRepresentation
Indicates that one entity serves as a model, depiction, or abstraction of an ecosystem, capturing its components, structure, or dynamics.
-
D.
ecoregion
chosen
Indicates that one entity is located within, associated with, or belongs to the same ecological region as 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7a66d3881908f5aec4ccd11d60d |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.