Triple
T28163388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Field, Tinian |
E714956
|
entity |
| Predicate | aircraftLaunched |
P4685
|
FINISHED |
| Object | Enola Gay |
—
|
NE NERFINISHED |
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: Enola Gay | Statement: [North Field, Tinian, aircraftLaunched, Enola Gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftLaunched Context triple: [North Field, Tinian, aircraftLaunched, Enola Gay]
-
A.
launchedAircraftIn
chosen
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
B.
inauguralFlightVehicle
Indicates that the subject is the vehicle used to operate the inaugural (first-ever) flight of a given service or route.
-
C.
firstFlightLaunchVehicle
Indicates that the subject is the launch vehicle used for an entity’s first flight.
-
D.
launchVehicleDesignation
Indicates the specific launch vehicle assigned or designated to carry a payload or mission into space.
-
E.
launchVehicleSupported
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 10:07 p.m.