Triple
T9890249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenzhou 12 |
E181432
|
entity |
| Predicate | EVAActivity |
P66429
|
FINISHED |
| Object | installation of external equipment on Tianhe |
—
|
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: installation of external equipment on Tianhe | Statement: [Shenzhou 12, EVAActivity, installation of external equipment on Tianhe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAActivity Context triple: [Shenzhou 12, EVAActivity, installation of external equipment on Tianhe]
-
A.
EVAobjective
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
B.
EVAcrew
Indicates that the subject is a crew member participating in an extravehicular activity (spacewalk).
-
C.
performedEVA
Indicates that an entity has carried out an extravehicular activity (EVA), such as a spacewalk, outside a spacecraft or space station.
-
D.
evidenceOfActivity
Indicates that there is information or data supporting the occurrence or performance of a particular activity or action.
-
E.
performActivities
chosen
Indicates that an entity carries out or engages in one or more specified activities or tasks.
- 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.