Triple
T20229579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Federation |
E495478
|
entity |
| Predicate | annexationOfCrimea |
P139321
|
FINISHED |
| Object | 2014 |
—
|
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 | Statement: [Russian Federation, annexationOfCrimea, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexationOfCrimea Context triple: [Russian Federation, annexationOfCrimea, 2014]
-
A.
annexationControversy
Indicates a dispute or conflict over the legitimacy, process, or consequences of one entity annexing territory or authority from another.
-
B.
annexationOpposedBy
Indicates that an annexation is met with opposition or resistance from a specified party or entity.
-
C.
annexationPolicy
Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
-
D.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
-
E.
associatedWithCrimeanPeninsula
Indicates a relationship in which something or someone has a connection, relevance, or association to the Crimean Peninsula.
- F. None of above. chosen
Provenance (4 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fdc2590819089a946d16c6c0e59 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.