Triple
T18652960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodina Mat |
E455985
|
entity |
| Predicate | languageOfCurrentOfficialName |
P26955
|
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: [Rodina Mat, languageOfCurrentOfficialName, Ukrainian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCurrentOfficialName Context triple: [Rodina Mat, languageOfCurrentOfficialName, Ukrainian]
-
A.
hasLanguageOfOfficialName
chosen
Indicates that an entity’s official name is expressed in a specified language.
-
B.
formerOfficialNameLanguage
Indicates the language in which an entity’s former official name was expressed.
-
C.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
D.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
E.
officialLanguage
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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5501279d08190aeca36df89fee2b2 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.