Triple
T27343706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 first stage booster B1031 |
E684174
|
entity |
| Predicate | payloadOnSecondFlight |
P162204
|
FINISHED |
| Object | SES-10 communications satellite |
—
|
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 communications satellite | Statement: [Falcon 9 first stage booster B1031, payloadOnSecondFlight, SES-10 communications satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadOnSecondFlight Context triple: [Falcon 9 first stage booster B1031, payloadOnSecondFlight, SES-10 communications satellite]
-
A.
firstFlightPayload
Indicates that the object is the payload carried on an entity’s first flight.
-
B.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
C.
isSecondPilotOf
Indicates that one entity serves as the co-pilot or secondary pilot for another entity, typically an aircraft or flight.
-
D.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
-
E.
secondCrewedMission
Indicates that the mission is the second one to carry a crew.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba0fedc8190b63a546f7d893676 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:44 a.m.