Triple
T3771918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Belarus |
E83216
|
entity |
| Predicate | usesUniformStyle |
P2930
|
FINISHED |
| Object | Soviet-style uniforms with national insignia |
—
|
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: Soviet-style uniforms with national insignia | Statement: [Armed Forces of Belarus, usesUniformStyle, Soviet-style uniforms with national insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUniformStyle Context triple: [Armed Forces of Belarus, usesUniformStyle, Soviet-style uniforms with national insignia]
-
A.
usesUniform
chosen
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
B.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
-
C.
usedUniformColor
Indicates that multiple entities share or employed the same uniform color in a given context.
-
D.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
E.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc3219b881908a2f82126f9a679d |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.