Triple
T32137685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sloviansk |
E820815
|
entity |
| Predicate | hasBeenTargetIn |
P24107
|
FINISHED |
| Object | 2022 Russian invasion of Ukraine |
—
|
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: 2022 Russian invasion of Ukraine | Statement: [Sloviansk, hasBeenTargetIn, 2022 Russian invasion of Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenTargetIn Context triple: [Sloviansk, hasBeenTargetIn, 2022 Russian invasion of Ukraine]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
wasTargetDuring
chosen
Indicates that an entity served as the target of another entity or action during a specified time period or event.
-
C.
isTargetIn
Indicates that a specified entity lies within, or is contained inside, a given target region, set, or scope.
-
D.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
-
E.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 12:30 a.m.