Triple
T28599098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chyhyryn Raion |
E723855
|
entity |
| Predicate | usedLanguageDeFacto |
P237
|
FINISHED |
| Object | Ukrainian |
—
|
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: Ukrainian | Statement: [Chyhyryn Raion, usedLanguageDeFacto, Ukrainian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLanguageDeFacto Context triple: [Chyhyryn Raion, usedLanguageDeFacto, Ukrainian]
-
A.
deFactoLanguage
chosen
Indicates that a language is used in practice as the primary or common language in a context, even if it has no official legal status there.
-
B.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
C.
adoptedLanguage
Indicates that an entity has chosen and begun using a particular language, typically as its official, primary, or preferred means of communication.
-
D.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
E.
formerLanguage
Indicates that one entity was previously the language of another entity but is no longer in that role.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:23 a.m.