Triple
T8185685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianzhou cargo spacecraft |
E191175
|
entity |
| Predicate | propellantTransferCapability |
P81319
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tianzhou cargo spacecraft, propellantTransferCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellantTransferCapability Context triple: [Tianzhou cargo spacecraft, propellantTransferCapability, yes]
-
A.
propellantMass
Indicates the amount of propellant associated with or used by an object or system in a given context.
-
B.
propellantStorage
Indicates that one entity serves as a location or facility where propellant is stored for later use.
-
C.
propellantRatio
Indicates the proportional relationship between different propellant components used together in a propulsion system.
-
D.
propellantTypeUpperStage
Indicates the type of propellant used by the upper stage of a launch vehicle or rocket system.
-
E.
propellantTypeCoreStage
Indicates the type of propellant used in the core stage of a launch vehicle or rocket system.
- F. None of above. chosen
Provenance (4 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c52407c8190bd366fce6d4e02cd |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:41 p.m.