Triple
T38054743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship (SpaceX) |
E949868
|
entity |
| Predicate | firstOrbitalTestFlightDate |
P28718
|
FINISHED |
| Object | 2023-04-20 |
—
|
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: 2023-04-20 | Statement: [Starship (SpaceX), firstOrbitalTestFlightDate, 2023-04-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOrbitalTestFlightDate Context triple: [Starship (SpaceX), firstOrbitalTestFlightDate, 2023-04-20]
-
A.
firstOrbitalSuccessDate
Indicates the calendar date on which an entity achieved its first successful orbital mission.
-
B.
firstOrbitalLaunchAttemptDate
chosen
Indicates the calendar date on which an entity made its first attempt to launch a vehicle into orbit.
-
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.
firstSuccessfulOrbitalLaunch
Indicates that the event is the earliest instance in which a launch successfully placed a payload into a stable orbit around a celestial body.
-
E.
firstSuborbitalFlightDate
Indicates the calendar date on which an entity’s first suborbital flight occurred.
- 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.