Triple
T23973424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | START II |
E604296
|
entity |
| Predicate | RussianWithdrawal |
P154087
|
FINISHED |
| Object | 2002-06-14 |
—
|
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: 2002-06-14 | Statement: [START II, RussianWithdrawal, 2002-06-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RussianWithdrawal Context triple: [START II, RussianWithdrawal, 2002-06-14]
-
A.
participantReleasedByRussia
Indicates that a participant was freed from custody or control specifically by Russian authorities or entities.
-
B.
annexationOfCrimea
Indicates the political and territorial act by which one state unilaterally incorporated Crimea into its own sovereign control.
-
C.
RussiaControls
Indicates that Russia exercises authority, influence, or governing power over the specified entity or territory.
-
D.
importanceForRussia
Indicates that something holds particular strategic, political, economic, or cultural significance specifically for Russia.
-
E.
justificationClaimedByUSSR
Indicates that a particular justification or rationale was asserted or claimed by the USSR as the basis for its actions or positions.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dda91c8190af716bceb3225aee |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.