Triple
T29998590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Launch program |
E762098
|
entity |
| Predicate | rocketEngineSupplier |
P168805
|
FINISHED |
| Object | NPO Energomash |
—
|
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: NPO Energomash | Statement: [Sea Launch program, rocketEngineSupplier, NPO Energomash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rocketEngineSupplier Context triple: [Sea Launch program, rocketEngineSupplier, NPO Energomash]
-
A.
rocketEngine
Indicates that an entity functions as, or is equipped with, a rocket engine used to generate thrust for propulsion.
-
B.
solidRocketBoosterSupplier
Indicates that one entity serves as a supplier of solid rocket boosters to another entity.
-
C.
solidRocketBoosterManufacturer
Indicates that one entity is the manufacturer responsible for producing the solid rocket booster used by another entity.
-
D.
standardRocketMotor
Indicates that an entity functions as a standard rocket motor used for propulsion in a rocket system.
-
E.
rocketVariant
Indicates a specific version or configuration of a given rocket.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 6:40 p.m.