Triple
T27996767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin 1C sea-level |
E707032
|
entity |
| Predicate | usedOnVehicleStage |
P82971
|
FINISHED |
| Object | Falcon 9 first stage |
—
|
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: Falcon 9 first stage | Statement: [Merlin 1C sea-level, usedOnVehicleStage, Falcon 9 first stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnVehicleStage Context triple: [Merlin 1C sea-level, usedOnVehicleStage, Falcon 9 first stage]
-
A.
usedInStage
chosen
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
-
B.
usesStageRacing
Indicates that an entity employs or applies stage racing as a method, format, or strategy in its activities or operations.
-
C.
usedOnVehicleFamily
Indicates that something is designed or intended to be used on a particular family or category of vehicles.
-
D.
usesVehicleVariant
Indicates that one entity performs an action or function by employing a specific variant or version of a vehicle.
-
E.
usedAsVehicleFor
Indicates that one entity functions as a means of transportation or conveyance for another entity.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bab984881909efaa8099e38fdf1 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:53 p.m.