Triple
T12240293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1 |
E291710
|
entity |
| Predicate | firstSupersonicFlightDate |
P43655
|
FINISHED |
| Object | 1947-10-14 |
—
|
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: 1947-10-14 | Statement: [Bell X-1, firstSupersonicFlightDate, 1947-10-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSupersonicFlightDate Context triple: [Bell X-1, firstSupersonicFlightDate, 1947-10-14]
-
A.
firstSupersonicFlight
chosen
Indicates that the event represents the earliest instance in which an aircraft or object exceeded the speed of sound.
-
B.
firstSupersonicAircraftPowered
Indicates that the subject is the first aircraft to achieve supersonic flight using the specified power source or propulsion system.
-
C.
firstPoweredFlightDate
Indicates the calendar date on which an entity (typically an aircraft or spacecraft) achieved its first powered flight.
-
D.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
-
E.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.