Triple
T32977703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rovenky |
E843711
|
entity |
| Predicate | isInConflictRegion |
P21190
|
FINISHED |
| Object | War in Donbas |
—
|
NE NERFINISHED |
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: War in Donbas | Statement: [Rovenky, isInConflictRegion, War in Donbas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInConflictRegion Context triple: [Rovenky, isInConflictRegion, War in Donbas]
-
A.
endedConflictInRegion
Indicates that an entity brought a conflict within a specified region to an end.
-
B.
conflictRegion
chosen
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
C.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
D.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
E.
isKeyRegionIn
Indicates that a region plays a central or strategically important role within a larger area, system, or 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:22 a.m.