Triple
T23089514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonivka Road Bridge |
E575704
|
entity |
| Predicate | tacticalEffectOfDamage |
P78832
|
FINISHED |
| Object | disrupted Russian resupply across the Dnipro |
—
|
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: disrupted Russian resupply across the Dnipro | Statement: [Antonivka Road Bridge, tacticalEffectOfDamage, disrupted Russian resupply across the Dnipro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalEffectOfDamage Context triple: [Antonivka Road Bridge, tacticalEffectOfDamage, disrupted Russian resupply across the Dnipro]
-
A.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
B.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
C.
damageLeadsTo
chosen
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
D.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da8818481908d768a0462f3f837 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.