Triple
T8673516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E205857
|
entity |
| Predicate | firstPoweredFlightDate |
P84010
|
FINISHED |
| Object | 2020-05-25 |
—
|
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: 2020-05-25 | Statement: [LauncherOne, firstPoweredFlightDate, 2020-05-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPoweredFlightDate Context triple: [LauncherOne, firstPoweredFlightDate, 2020-05-25]
-
A.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
-
B.
firstCommercialFlightDate
Indicates the calendar date on which an entity’s first commercial flight or revenue-earning air service took place.
-
C.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
D.
firstFlightWithEngine
Indicates that the subject entity represents the first flight event in which the specified engine was used or operated.
-
E.
firstCrewedTestFlightYear
Indicates the calendar year in which an entity conducted its first test flight involving a human crew.
- F. None of above. chosen
Provenance (4 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491b807c81909563a34a947bc21a |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.