Triple
T15754750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas A-4 Skyhawk |
E381938
|
entity |
| Predicate | retiredFromUSMCFrontlineService |
P120201
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Douglas A-4 Skyhawk, retiredFromUSMCFrontlineService, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromUSMCFrontlineService Context triple: [Douglas A-4 Skyhawk, retiredFromUSMCFrontlineService, 1990s]
-
A.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
B.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
C.
hasMilitaryServiceEnd
Indicates the date or point in time at which an entity’s period of military service concludes.
-
D.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
-
E.
retiredFromIcebreakingService
Indicates that an entity has ceased performing icebreaking operations and is no longer in active icebreaking service.
- F. None of above. chosen
Provenance (4 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.