Triple
T16835216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M-MRD |
E409256
|
entity |
| Predicate | placeDestroyed |
P53686
|
FINISHED |
| Object | near Hrabove, Donetsk Oblast, Ukraine |
—
|
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: near Hrabove, Donetsk Oblast, Ukraine | Statement: [9M-MRD, placeDestroyed, near Hrabove, Donetsk Oblast, Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeDestroyed Context triple: [9M-MRD, placeDestroyed, near Hrabove, Donetsk Oblast, Ukraine]
-
A.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
-
B.
replacedStructureDemolished
Indicates that a structure which has been replaced by another has subsequently been demolished.
-
C.
locationOfDestruction
chosen
Indicates the place where a destruction event occurred or where something was destroyed.
-
D.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
E.
previousBuildingDemolished
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31aa44c8190b4f402f1898e6998 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.