Triple
T38054746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship (SpaceX) |
E949868
|
entity |
| Predicate | thirdIntegratedFlightTestDate |
P156359
|
FINISHED |
| Object | 2024-03-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: 2024-03-14 | Statement: [Starship (SpaceX), thirdIntegratedFlightTestDate, 2024-03-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdIntegratedFlightTestDate Context triple: [Starship (SpaceX), thirdIntegratedFlightTestDate, 2024-03-14]
-
A.
fourthIntegratedFlightTestDate
Indicates the date on which the fourth integrated flight test is scheduled or occurred.
-
B.
thirdTestDate
chosen
Indicates the date on which a third test or testing event takes place in relation to an entity.
-
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.
secondMannedTestDate
Indicates the calendar date on which the second manned (crewed) test of something is scheduled or occurred.
-
E.
firstUncrewedTestFlight
Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:21 p.m.