Triple
T32508319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenzhou 11 |
E830859
|
entity |
| Predicate | reentryModuleRecovery |
P101386
|
FINISHED |
| Object | successful |
—
|
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: successful | Statement: [Shenzhou 11, reentryModuleRecovery, successful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryModuleRecovery Context triple: [Shenzhou 11, reentryModuleRecovery, successful]
-
A.
reentryModule
Indicates that one entity serves as the reentry module or component used for returning from space or a high-altitude environment.
-
B.
reentryRecovery
chosen
Indicates the process or capability of safely recovering an object or vehicle after it reenters an atmosphere from space or high-altitude flight.
-
C.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
D.
reentryProtection
Indicates that an entity is safeguarded against harmful effects or risks associated with reentering a system, environment, or jurisdiction.
-
E.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44d21648190ada905d52e251b1f |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.