Triple
T27343704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 first stage booster B1031 |
E684174
|
entity |
| Predicate | secondLandingOutcome |
P182746
|
FINISHED |
| Object | successful |
—
|
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: successful | Statement: [Falcon 9 first stage booster B1031, secondLandingOutcome, successful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLandingOutcome Context triple: [Falcon 9 first stage booster B1031, secondLandingOutcome, successful]
-
A.
secondLaunchOutcome
Indicates the result or status of the entity’s second launch attempt or event.
-
B.
secondaryOutcome
Indicates that an outcome occurs as a secondary, subordinate, or additional result relative to a primary outcome.
-
C.
secondTermSucceededBy
Indicates that the referenced second term is immediately followed or replaced by another term in a sequence or succession.
-
D.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
E.
secondPhaseLocation
Indicates the location where the second phase of an event, process, or operation takes place.
- 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_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 27, 2026, 11:44 a.m.