Triple
T31793212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing Commercial Crew program |
E811523
|
entity |
| Predicate | secondUncrewedOrbitalFlightYear |
P196793
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Boeing Commercial Crew program, secondUncrewedOrbitalFlightYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondUncrewedOrbitalFlightYear Context triple: [Boeing Commercial Crew program, secondUncrewedOrbitalFlightYear, 2022]
-
A.
secondSpaceflightYear
Indicates the year in which an entity conducted or experienced its second spaceflight.
-
B.
firstOrbitalLaunchAttemptDate
Indicates the calendar date on which an entity made its first attempt to launch a vehicle into orbit.
-
C.
firstSuccessfulCrewedMissionDate
Indicates the calendar date on which the first crewed mission associated with the subject was successfully completed.
-
D.
firstCrewedLaunchFrom
Indicates the location from which an entity conducted its first crewed (human-carrying) launch.
-
E.
firstOrbitalSuccessDate
Indicates the calendar date on which an entity achieved its first successful orbital mission.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: April 30, 2026, 11:39 p.m.