Triple
T6640448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vought F4U Corsair |
E150573
|
entity |
| Predicate | retiredFromUSServiceYear |
P19195
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Vought F4U Corsair, retiredFromUSServiceYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromUSServiceYear Context triple: [Vought F4U Corsair, retiredFromUSServiceYear, 1953]
-
A.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
B.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
C.
hasMilitaryServiceEnd
chosen
Indicates the date or point in time at which an entity’s period of military service concludes.
-
D.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
E.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.