Triple
T127685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Army |
E2584
|
entity |
| Predicate | languageOfCommand |
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: [Red Army, languageOfCommand, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCommand Context triple: [Red Army, languageOfCommand, Russian]
-
A.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
B.
languageOfInterface
Indicates the language used by or presented in a user interface.
-
C.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
D.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
E.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
- F. None of above. chosen
Provenance (4 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25763ccf8819094e8dffb2ff98480 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575d8a648190ad8e10d4b04e5e07 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.