Triple
T20526446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Ajax |
E503947
|
entity |
| Predicate | yearOfDeclassification |
P3246
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Operation Ajax, yearOfDeclassification, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfDeclassification Context triple: [Operation Ajax, yearOfDeclassification, 2013]
-
A.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
B.
destructionYear
Indicates the year in which an entity was destroyed or ceased to exist due to destructive events or actions.
-
C.
declassified
chosen
Indicates that information or material has been officially downgraded from a restricted or secret status, making it accessible to a wider audience or the public.
-
D.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a066402081909dd53830eb637ad0 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.