Triple
T36666550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Savage |
E905279
|
entity |
| Predicate | fictionalAircraftType |
P199476
|
FINISHED |
| Object | B-17 Flying Fortress |
E34359
|
NE 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: B-17 Flying Fortress | Statement: [Frank Savage, fictionalAircraftType, B-17 Flying Fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalAircraftType Context triple: [Frank Savage, fictionalAircraftType, B-17 Flying Fortress]
-
A.
usesFictionalAircraftType
Indicates that an entity makes use of, operates, or features a type of aircraft that is fictional rather than real.
-
B.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
C.
portraysAircraft
Indicates that one entity visually represents or depicts an aircraft in some medium or form.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
- F. None of above. chosen
Provenance (5 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20d654fc81908216ac9680f56464 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: May 3, 2026, 4:12 p.m.