Triple
T9890311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long March 5B |
E181433
|
entity |
| Predicate | oxidizerBoosters |
P78243
|
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: [Long March 5B, oxidizerBoosters, liquid oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxidizerBoosters Context triple: [Long March 5B, oxidizerBoosters, liquid oxygen]
-
A.
oxidizer
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.
oxidizerTank
chosen
Indicates that one entity functions as an oxidizer tank associated with, containing, or supplying oxidizer for another entity or system.
-
C.
oxidizerState
Indicates the physical or chemical state (e.g., solid, liquid, gas, concentration, or phase condition) in which an oxidizing agent exists during a reaction or process.
-
D.
oxidizerTankMaterial
Indicates the material from which an oxidizer tank is constructed or composed.
-
E.
boosterType
Indicates the specific kind or category of booster associated with an entity or action.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.