Triple
T36957959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armadillo Aerospace |
E914235
|
entity |
| Predicate | propellantUsed |
P42806
|
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: [Armadillo Aerospace, propellantUsed, liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellantUsed Context triple: [Armadillo Aerospace, propellantUsed, liquid oxygen]
-
A.
propellantCapacity
Indicates the amount of propellant a system, such as a rocket or spacecraft, is capable of storing or carrying.
-
B.
propellantMass
Indicates the amount of propellant associated with or used by an object or system in a given context.
-
C.
propellantComponent
Indicates that one substance serves as a constituent part of a propellant formulation used in a propulsion or thrust-generating system.
-
D.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
E.
usesPropellantType
chosen
Indicates that one entity operates or functions using a specific type of propellant as its fuel or reaction mass.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.