Triple
T32546643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magyar Néphadsereg |
E831862
|
entity |
| Predicate | commandLanguageInAlliance |
P6537
|
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: [Magyar Néphadsereg, commandLanguageInAlliance, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandLanguageInAlliance Context triple: [Magyar Néphadsereg, commandLanguageInAlliance, Russian]
-
A.
languageOfCommand
chosen
Indicates that a specified language is the one in which a given command is expressed or issued.
-
B.
combatantLanguage
Indicates the language used by a combatant in a conflict or competitive interaction.
-
C.
languageOfUnion
Indicates that a specified language is officially used or recognized as a language of a particular union or union-level entity.
-
D.
queryLanguage
Indicates that an entity uses or is associated with a particular language for formulating and executing queries.
-
E.
officialLanguageOfRules
Indicates that a specified language is the formally designated language used for the rules or regulations of a given entity or system.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:02 a.m.