Triple
T33985043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine |
E871388
|
entity |
| Predicate | conflictRegionIncludes |
P123563
|
FINISHED |
| Object | 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: Donbas | Statement: [Ukraine, conflictRegionIncludes, Donbas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictRegionIncludes Context triple: [Ukraine, conflictRegionIncludes, Donbas]
-
A.
conflictRegion
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
B.
endedConflictInRegion
Indicates that an entity brought a conflict within a specified region to an end.
-
C.
hasBorderConflictWith
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
D.
regionContains
chosen
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:50 a.m.