Triple
T8055439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin engine family |
E187986
|
entity |
| Predicate | member |
P10
|
FINISHED |
| Object | Merlin 1C |
E17817
|
NE 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: Merlin 1C | Statement: [Merlin engine family, member, Merlin 1C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Merlin 1C Context triple: [Merlin engine family, member, Merlin 1C]
-
A.
Merlin 1C
chosen
Merlin 1C is a liquid-fueled rocket engine developed by SpaceX for use on early Falcon rockets, notable for its role in pioneering the company’s orbital launch capabilities.
-
B.
Merlin 1B
Merlin 1B is an early variant of SpaceX’s Merlin rocket engine, used to power initial versions of the Falcon 9 launch vehicle.
-
C.
Merlin 1A
Merlin 1A is the first-generation liquid-fueled rocket engine developed by SpaceX for early Falcon 1 launches.
-
D.
Merlin 1D
Merlin 1D is a liquid-fueled rocket engine developed by SpaceX, known for powering the first stage of the Falcon 9 launch vehicle with high thrust and reusability.
-
E.
Merlin HM2
The Merlin HM2 is a British Royal Navy maritime patrol and anti-submarine warfare helicopter equipped with advanced sensors and weapons for operations from warships and shore bases.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa16804819094926ff2ff053c80 |
completed | March 31, 2026, 3:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbe5c1850819097f82cfa7f582e8d |
completed | April 1, 2026, 6:42 a.m. |
Created at: March 30, 2026, 5:25 p.m.