Triple
T1599553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing B-17 Flying Fortress |
E34359
|
entity |
| Predicate | retiredFromUSService |
P19195
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Boeing B-17 Flying Fortress, retiredFromUSService, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromUSService Context triple: [Boeing B-17 Flying Fortress, retiredFromUSService, 1949]
-
A.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
B.
hasMilitaryServiceEnd
chosen
Indicates the date or point in time at which an entity’s period of military service concludes.
-
C.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
D.
retired
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
-
E.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a916d413f08190a4e137e5ed262e25 |
completed | March 5, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69a907bfb39c8190a31e0be14d3d52e6 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.