Triple
T10241522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | northeastern Ukraine |
E243602
|
entity |
| Predicate | hasConflictRole |
P6060
|
FINISHED |
| Object | frontline region in the Russo-Ukrainian War |
—
|
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: frontline region in the Russo-Ukrainian War | Statement: [northeastern Ukraine, hasConflictRole, frontline region in the Russo-Ukrainian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConflictRole Context triple: [northeastern Ukraine, hasConflictRole, frontline region in the Russo-Ukrainian War]
-
A.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
B.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
C.
hasConflictScale
Indicates the degree or intensity of conflict present in a given relationship, situation, or interaction.
-
D.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
E.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:24 a.m.