Triple
T23973408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | START II |
E604296
|
entity |
| Predicate | reasonNotInForce |
P154085
|
FINISHED |
| Object | Russian withdrawal before entry into force |
—
|
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: Russian withdrawal before entry into force | Statement: [START II, reasonNotInForce, Russian withdrawal before entry into force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonNotInForce Context triple: [START II, reasonNotInForce, Russian withdrawal before entry into force]
-
A.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
B.
reasonNextNotHeld
Indicates that the specified reason explains why the immediately following event, state, or condition did not occur or was not maintained.
-
C.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
-
D.
reasonForNonOperation
Indicates the specific cause or explanation for why an entity, system, or process is not currently operating or functioning.
-
E.
reasonForNotCompletion
Indicates the explanation or cause for why a task, process, or obligation was not completed.
- 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.