Triple
T33334982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Russian offensive on Sumy Oblast |
E853509
|
entity |
| Predicate | borderRegionInvolved |
P30106
|
FINISHED |
| Object | Kursk Oblast |
—
|
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: Kursk Oblast | Statement: [2022 Russian offensive on Sumy Oblast, borderRegionInvolved, Kursk Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegionInvolved Context triple: [2022 Russian offensive on Sumy Oblast, borderRegionInvolved, Kursk Oblast]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderRegionsInclude
Indicates that the specified border area encompasses or contains the referenced regions within its boundaries.
-
C.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
D.
borderRegionRole
Indicates a role or function that an entity has specifically in relation to a border region or border area.
-
E.
borderRegionPresence
chosen
Indicates the presence or occurrence of something within or along a border region between areas or territories.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 1, 2026, 1:34 a.m.