Triple
T13085859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-Stoff |
E310333
|
entity |
| Predicate | reactsHypergolicallyWith |
P24601
|
FINISHED |
| Object | T-Stoff |
—
|
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: T-Stoff | Statement: [C-Stoff, reactsHypergolicallyWith, T-Stoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactsHypergolicallyWith Context triple: [C-Stoff, reactsHypergolicallyWith, T-Stoff]
-
A.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
B.
chemicallyRelatedTo
chosen
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
-
C.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
D.
reactant
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
-
E.
propellantUpperStageOxidizer
Indicates that the specified oxidizer is used as the oxidizing component in the propellant of an upper-stage rocket.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.