Triple
T29713996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MVS |
E751858
|
entity |
| Predicate | fullNameInUkrainian |
P138513
|
FINISHED |
| Object | Міністерство внутрішніх справ України |
—
|
NE NERFINISHED |
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: [MVS, fullNameInUkrainian, Міністерство внутрішніх справ України]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameInUkrainian Context triple: [MVS, fullNameInUkrainian, Міністерство внутрішніх справ України]
-
A.
UkrainianName
Indicates that an entity has a name that is in the Ukrainian language or follows Ukrainian naming conventions.
-
B.
hasOfficialNameInUkrainian
chosen
Indicates that an entity has an officially recognized name expressed in the Ukrainian language.
-
C.
hasNameInRusyn
Indicates that an entity has a specific name or label expressed in the Rusyn language.
-
D.
CyrillicName
Indicates that an entity has a name written in the Cyrillic script.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 7:32 p.m.