Triple
T27343698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 first stage booster B1031 |
E684174
|
entity |
| Predicate | secondFlightMission |
P162204
|
FINISHED |
| Object | SES-10 |
—
|
NE NERFINISHED |
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: SES-10 | Statement: [Falcon 9 first stage booster B1031, secondFlightMission, SES-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondFlightMission Context triple: [Falcon 9 first stage booster B1031, secondFlightMission, SES-10]
-
A.
secondCrewedMission
Indicates that the mission is the second one to carry a crew.
-
B.
secondReplacementMission
Indicates that an entity undertakes or is assigned to a second mission specifically intended to replace or relieve a prior mission or its participants.
-
C.
payloadOnSecondFlight
chosen
Indicates that a payload is carried or scheduled to be carried on the second flight in a sequence of flights.
-
D.
aircraftSecondaryMission
Indicates the secondary mission or role that an aircraft is intended or configured to perform in addition to its primary mission.
-
E.
pilotLaterMission
Indicates that an entity serves as the pilot of a mission that occurs after a referenced or earlier mission.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 11:44 a.m.