Triple
T10660914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dassault Mirage IV |
E251220
|
entity |
| Predicate | retiredFromNuclearRole |
P2644
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Dassault Mirage IV, retiredFromNuclearRole, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromNuclearRole Context triple: [Dassault Mirage IV, retiredFromNuclearRole, 1996]
-
A.
retiredFromTankerRole
Indicates that an entity has ceased serving in a tanker capacity or role.
-
B.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
C.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
D.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
E.
removedFromPublicDuties
Indicates that an entity has been taken out of roles or responsibilities that involve serving or representing the public.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e017f97c8190b22765a6f1e6719d |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.