Triple
T33489649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MO SR |
E857703
|
entity |
| Predicate | officialNameSlovak |
P25642
|
FINISHED |
| Object | Ministerstvo obrany Slovenskej republiky |
—
|
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: Ministerstvo obrany Slovenskej republiky | Statement: [MO SR, officialNameSlovak, Ministerstvo obrany Slovenskej republiky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameSlovak Context triple: [MO SR, officialNameSlovak, Ministerstvo obrany Slovenskej republiky]
-
A.
officialAbbreviationInSlovak
Indicates that an entity has a specific official abbreviation when written in the Slovak language.
-
B.
nameInSlovak
chosen
Indicates that an entity is known or referred to by a specific name in the Slovak language.
-
C.
officialNameInSlovene
Indicates the officially recognized name of an entity when expressed in the Slovene language.
-
D.
historicalNameInSlovak
Indicates that an entity is known or referred to by a particular historical name in the Slovak language.
-
E.
czechName
Indicates that an entity has a name in the Czech language, specifying the Czech-language form of its name.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 1, 2026, 1:38 a.m.