Triple
T12852457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia–Ukraine maritime disputes |
E307357
|
entity |
| Predicate | escalatedAfter |
P96217
|
FINISHED |
| Object | 2014 annexation of Crimea |
—
|
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: 2014 annexation of Crimea | Statement: [Russia–Ukraine maritime disputes, escalatedAfter, 2014 annexation of Crimea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escalatedAfter Context triple: [Russia–Ukraine maritime disputes, escalatedAfter, 2014 annexation of Crimea]
-
A.
escalationDate
Indicates the date on which an issue, case, or situation was formally escalated to a higher level of attention or authority.
-
B.
significantlyIntensifiedAfter
Indicates that one condition, effect, or quality became much stronger or more pronounced following another event or state.
-
C.
sawMajorEscalation
chosen
Indicates that the relationship or situation experienced a significant and rapid increase in intensity, scale, or severity.
-
D.
caseEscalatedTo
Indicates that a case has been transferred from a lower level of handling to a higher level of authority or expertise for further attention or resolution.
-
E.
laterRaised
Indicates that one entity was raised, elevated, or brought up at a time subsequent to another referenced event or state.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.