Triple
T17080685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pripyat |
E414459
|
entity |
| Predicate | languageUsedOfficially |
P236
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Pripyat, languageUsedOfficially, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedOfficially Context triple: [Pripyat, languageUsedOfficially, Russian]
-
A.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
B.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
C.
idiomasOficiales
Indicates that one or more languages are officially recognized or designated for use by a given entity (such as a country, region, or institution).
-
D.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
E.
officialLanguage
chosen
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.