Triple
T4955704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bakhmut |
E111274
|
entity |
| Predicate | symbolicForUkraine |
P129
|
FINISHED |
| Object | resistance and resilience |
—
|
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: resistance and resilience | Statement: [Battle of Bakhmut, symbolicForUkraine, resistance and resilience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicForUkraine Context triple: [Battle of Bakhmut, symbolicForUkraine, resistance and resilience]
-
A.
symbolizesNationalSovereignty
Indicates that something serves as a representation or emblem of a nation's sovereignty or independent authority.
-
B.
UkrainianName
Indicates that an entity has a name that is in the Ukrainian language or follows Ukrainian naming conventions.
-
C.
usesSovietSymbols
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
supporterSymbol
Indicates that one entity serves as a symbolic representation or emblem of support for another entity.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71babb44819085b4cd4864433e79 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.