Triple
T19565125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itelmen people |
E489560
|
entity |
| Predicate | officialStatusInRussia |
P13676
|
FINISHED |
| Object | Indigenous minority |
—
|
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: Indigenous minority | Statement: [Itelmen people, officialStatusInRussia, Indigenous minority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStatusInRussia Context triple: [Itelmen people, officialStatusInRussia, Indigenous minority]
-
A.
statusInRussia
chosen
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
B.
legalStatusClaimedByRussia
Indicates that Russia asserts a particular legal status or claim over the referenced entity or territory.
-
C.
statusInRussianEmpire
Indicates the legal or social standing an entity held within the political and administrative system of the Russian Empire.
-
D.
officialStatusInTerritory
Indicates that an entity holds a recognized official status, role, or designation within a specified territory or jurisdiction.
-
E.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f76b220819096e668534c6bac67 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.