Triple
T27929422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion program |
E707936
|
entity |
| Predicate | firstUncrewedTestFlightDate |
P24224
|
FINISHED |
| Object | 2014-12-05 |
—
|
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: 2014-12-05 | Statement: [Orion program, firstUncrewedTestFlightDate, 2014-12-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUncrewedTestFlightDate Context triple: [Orion program, firstUncrewedTestFlightDate, 2014-12-05]
-
A.
firstUncrewedTestFlight
chosen
Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
-
B.
firstUncrewedTestFlightMission
Indicates that the subject is the first mission in which a spacecraft or launch system is tested in flight without any crew onboard.
-
C.
firstMannedTestDate
Indicates the calendar date on which the first manned (crewed) test of something—such as a vehicle, system, or mission—was conducted.
-
D.
firstSuborbitalFlightDate
Indicates the calendar date on which an entity’s first suborbital flight occurred.
-
E.
firstCrewedFlightDate
Indicates the calendar date on which an entity undertook its first flight carrying human crew.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 27, 2026, 7:02 p.m.