Triple
T23006611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Belarus |
E572786
|
entity |
| Predicate | sovietSymbolismRetainedFrom |
P42258
|
FINISHED |
| Object | flag of the Byelorussian SSR |
—
|
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: flag of the Byelorussian SSR | Statement: [Flag of Belarus, sovietSymbolismRetainedFrom, flag of the Byelorussian SSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietSymbolismRetainedFrom Context triple: [Flag of Belarus, sovietSymbolismRetainedFrom, flag of the Byelorussian SSR]
-
A.
usesSovietSymbols
chosen
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
-
B.
sharesSovietLegacyWith
Indicates that two entities have a common historical, political, or cultural background rooted in the former Soviet Union.
-
C.
sovietHistory
Indicates a relationship where an entity is associated with, pertains to, or is characterized by the history of the Soviet Union.
-
D.
sovietStrength
Indicates the level or degree of strength, power, or capability associated with the Soviet side in a given context or interaction.
-
E.
sovietPeriodName
Indicates that the object is the name used for the subject during the Soviet period.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835706dc8190b3f9743c0f336bb2 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.