Triple
T32386690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China's crewed spaceflight program |
E827560
|
entity |
| Predicate | cargoSpacecraftType |
P132160
|
FINISHED |
| Object | Tianzhou |
—
|
NE NERFINISHED |
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: Tianzhou | Statement: [China's crewed spaceflight program, cargoSpacecraftType, Tianzhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoSpacecraftType Context triple: [China's crewed spaceflight program, cargoSpacecraftType, Tianzhou]
-
A.
usedCargoSpacecraftType
chosen
Indicates that a particular type of cargo spacecraft was employed or utilized in a given mission or context.
-
B.
featuresSpacecraft
Indicates that one entity includes, presents, or prominently involves a spacecraft as part of its content, composition, or subject matter.
-
C.
spacecraftTypeSupported
Indicates that a system, facility, or service is capable of accommodating or operating a specified type of spacecraft.
-
D.
isOnSpacecraftType
Indicates that one entity is currently aboard or assigned to a spacecraft of a specified type.
-
E.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
- 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_69f6c1d26e608190abfa275a4c02a3ce |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.