Triple
T8970962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INF Treaty |
E214263
|
entity |
| Predicate | USWithdrawalEffective |
P12347
|
FINISHED |
| Object | 2019-08-02 |
—
|
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: 2019-08-02 | Statement: [INF Treaty, USWithdrawalEffective, 2019-08-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USWithdrawalEffective Context triple: [INF Treaty, USWithdrawalEffective, 2019-08-02]
-
A.
withdrawalAgreement
Indicates an agreement under which one party formally withdraws from a relationship, arrangement, or organization under specified terms and conditions.
-
B.
withdrawn
Indicates that an entity has removed or taken back a previously offered, submitted, or available item, action, or commitment.
-
C.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
D.
dateOfBrexit
Indicates the specific calendar date on which Brexit (the United Kingdom’s withdrawal from the European Union) formally took place.
-
E.
withdrawalDate
chosen
Indicates the date on which a withdrawal action occurs or is recorded.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67672c108190919ae6ca69b6291f |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.