Triple
T4089023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Comprehensive Plan of Action |
E87659
|
entity |
| Predicate | withdrawalAnnouncementDate |
P429
|
FINISHED |
| Object | 2018-05-08 |
—
|
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: 2018-05-08 | Statement: [Joint Comprehensive Plan of Action, withdrawalAnnouncementDate, 2018-05-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawalAnnouncementDate Context triple: [Joint Comprehensive Plan of Action, withdrawalAnnouncementDate, 2018-05-08]
-
A.
withdrawalDate
Indicates the date on which a withdrawal action occurs or is recorded.
-
B.
withdrawalAnnouncedBy
Indicates that an entity’s withdrawal (e.g., from an agreement, position, or situation) has been publicly announced or declared by a specified agent or source.
-
C.
discontinuationAnnouncementDate
Indicates the date on which an official announcement is made that something (such as a product, service, or feature) will be discontinued.
-
D.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
E.
withdrawalNoticePeriod
Indicates the required amount of time that must pass between giving notice and executing a withdrawal.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.