Triple
T32220393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8th Estonian Rifle Corps |
E823047
|
entity |
| Predicate | languageUsedByTroops |
P10179
|
FINISHED |
| Object | Estonian |
—
|
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: Estonian | Statement: [8th Estonian Rifle Corps, languageUsedByTroops, Estonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedByTroops Context triple: [8th Estonian Rifle Corps, languageUsedByTroops, Estonian]
-
A.
militaryBranchLanguage
Indicates the language or languages officially used or primarily associated with a particular military branch.
-
B.
combatantLanguage
chosen
Indicates the language used by a combatant in a conflict or competitive interaction.
-
C.
languageOfMilitaryService
Indicates the language in which a person’s military service was conducted or officially recorded.
-
D.
militaryLanguage
Indicates that the communication or expression is conveyed using military-specific terminology, style, or jargon.
-
E.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 1, 2026, 12:38 a.m.