Triple
T27343708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 first stage booster B1031 |
E684174
|
entity |
| Predicate | payloadOnFirstFlight |
P12519
|
FINISHED |
| Object | Dragon CRS-8 cargo spacecraft |
—
|
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: Dragon CRS-8 cargo spacecraft | Statement: [Falcon 9 first stage booster B1031, payloadOnFirstFlight, Dragon CRS-8 cargo spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadOnFirstFlight Context triple: [Falcon 9 first stage booster B1031, payloadOnFirstFlight, Dragon CRS-8 cargo spacecraft]
-
A.
payloadOnSecondFlight
Indicates that a payload is carried or scheduled to be carried on the second flight in a sequence of flights.
-
B.
firstFlightPayload
chosen
Indicates that the object is the payload carried on an entity’s first flight.
-
C.
firstFlightOutcome
Indicates the result or status of an entity’s initial flight attempt or maiden flight event.
-
D.
firstFlightBody
Indicates that the subject entity is the first aircraft or spacecraft body used for a particular flight or mission.
-
E.
testPilotOnFirstFlight
Indicates that the person served as the test pilot during the inaugural flight of an aircraft or aerospace vehicle.
- 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_69f62ba0fedc8190b63a546f7d893676 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:44 a.m.