Triple
T4088997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Comprehensive Plan of Action |
E87659
|
entity |
| Predicate | hasMilestone |
P52327
|
FINISHED |
| Object | Implementation Day |
—
|
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: Implementation Day | Statement: [Joint Comprehensive Plan of Action, hasMilestone, Implementation Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilestone Context triple: [Joint Comprehensive Plan of Action, hasMilestone, Implementation Day]
-
A.
hitsMilestone
chosen
Indicates that an entity reaches or achieves a predefined milestone or target in a process, project, or progression.
-
B.
hasMissionActivity
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
-
C.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in time.
-
D.
hasDeliverable
Indicates that one entity is associated with, responsible for, or produces a specific deliverable.
-
E.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
- 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.