Triple
T21324297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 521 |
E525707
|
entity |
| Predicate | coreStageOxidizer |
P103174
|
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: [Atlas V 521, coreStageOxidizer, liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreStageOxidizer Context triple: [Atlas V 521, coreStageOxidizer, liquid oxygen]
-
A.
coreStageBehavior
Indicates the fundamental or default way an entity acts or responds in a given context or process.
-
B.
coreStageType
Indicates the specific kind or classification of a core stage within a larger process, system, or lifecycle.
-
C.
coreStageEngineType
Indicates the specific type or model of engine used in the core stage of a launch vehicle or rocket.
-
D.
laterOxidizer
Indicates that one oxidizer occurs or is applied after another in time within a given process or sequence.
-
E.
usedWithCoreStage
chosen
Indicates that one entity is employed or functions in conjunction with a core stage component within a larger system or process.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed652c881909b0db482bc090993 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:40 p.m.