Triple
T334099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon Heavy |
E6685
|
entity |
| Predicate | oxidizerType |
P7195
|
FINISHED |
| Object | liquid oxygen |
—
|
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: liquid oxygen | Statement: [Falcon Heavy, oxidizerType, liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxidizerType Context triple: [Falcon Heavy, oxidizerType, liquid oxygen]
-
A.
oxidizer
chosen
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.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
C.
odor
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
D.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
E.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac641708190b85fa21368e5de8e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.