Triple
T36572856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLV |
E902163
|
entity |
| Predicate | stage3Propellant |
P38966
|
FINISHED |
| Object | Solid |
—
|
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: Solid | Statement: [SLV, stage3Propellant, Solid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stage3Propellant Context triple: [SLV, stage3Propellant, Solid]
-
A.
thirdStagePropellant
chosen
Indicates that an entity serves as the propellant used in the third stage of a multi-stage rocket or launch vehicle.
-
B.
propellantStage3
Indicates that an entity serves as or is associated with the third stage of a multi-stage propellant or propulsion system.
-
C.
fourthStagePropellant
Indicates that the specified propellant is used in the fourth stage of a multi-stage rocket or launch vehicle.
-
D.
propulsionStage
Indicates a specific phase or stage within a propulsion or thrust-generating process.
-
E.
thirdStageOxidizer
Indicates that an oxidizer component is associated with and used during the third stage of a multi-stage propulsion or rocket system.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.