Triple
T10037755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital Maneuvering System |
E205214
|
entity |
| Predicate | storedPropellants |
P39481
|
FINISHED |
| Object | in tanks within each OMS pod |
—
|
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: in tanks within each OMS pod | Statement: [Orbital Maneuvering System, storedPropellants, in tanks within each OMS pod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storedPropellants Context triple: [Orbital Maneuvering System, storedPropellants, in tanks within each OMS pod]
-
A.
propellantStorage
chosen
Indicates that one entity serves as a location or facility where propellant is stored for later use.
-
B.
propellantForm
Indicates the physical or chemical form in which a propellant is present or used in a system.
-
C.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
D.
usesPropellantType
Indicates that one entity operates or functions using a specific type of propellant as its fuel or reaction mass.
-
E.
solidBoosterPropellantType
Indicates the type or composition of propellant used in a solid rocket booster.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcede428c8190ae115dc3425f9b0e |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.