Triple
T3130997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interim Cryogenic Propulsion Stage |
E65412
|
entity |
| Predicate | oxidizerTankMaterial |
P45547
|
FINISHED |
| Object | aluminum-lithium alloy |
—
|
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: aluminum-lithium alloy | Statement: [Interim Cryogenic Propulsion Stage, oxidizerTankMaterial, aluminum-lithium alloy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxidizerTankMaterial Context triple: [Interim Cryogenic Propulsion Stage, oxidizerTankMaterial, aluminum-lithium alloy]
-
A.
oxidizer
Indicates a relationship where one entity acts as an oxidizing agent that accepts electrons from, or promotes the oxidation of, another entity in a chemical process.
-
B.
fuelTankMaterial
Indicates the material from which a fuel tank is made.
-
C.
mainTankName
Indicates that the subject entity has the specified name as its primary or main tank designation.
-
D.
usedExternalTank
Indicates that an entity made use of an external tank as part of its operation or activity.
-
E.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada54b0e688190b691771f17f4c721 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.