Triple
T32386930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Complex 201 |
E827566
|
entity |
| Predicate | supportsPropellant |
P39481
|
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: [Launch Complex 201, supportsPropellant, liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPropellant Context triple: [Launch Complex 201, supportsPropellant, liquid oxygen]
-
A.
usesPropellantType
Indicates that one entity operates or functions using a specific type of propellant as its fuel or reaction mass.
-
B.
propellantStorage
chosen
Indicates that one entity serves as a location or facility where propellant is stored for later use.
-
C.
propellantComponent
Indicates that one substance serves as a constituent part of a propellant formulation used in a propulsion or thrust-generating system.
-
D.
hasPropellantTanks
Indicates that an entity possesses or is equipped with one or more propellant tanks used to store fuel or reaction mass.
-
E.
propellantPhase
Indicates the physical state or phase (e.g., solid, liquid, gas) that the propellant is in under specified conditions.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.