Triple
T23336181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Зея |
E591591
|
entity |
| Predicate | часть света |
P40571
|
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.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
B.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
C.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
-
D.
continentSystem
Indicates a relationship where a continent is part of, or associated with, a particular planetary or geographic system.
-
E.
worldRegion
chosen
Indicates that one entity is a geographic region that encompasses, contains, or is associated with the other entity within the world.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.