Triple
T33095994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-07M |
E846909
|
entity |
| Predicate | reentryModuleType |
P92794
|
FINISHED |
| Object | Soyuz descent module |
—
|
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: Soyuz descent module | Statement: [Soyuz TMA-07M, reentryModuleType, Soyuz descent module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryModuleType Context triple: [Soyuz TMA-07M, reentryModuleType, Soyuz descent module]
-
A.
reentryModule
chosen
Indicates that one entity serves as the reentry module or component used for returning from space or a high-altitude environment.
-
B.
reentryMode
Indicates the mode or method by which an entity returns or is brought back into a system, environment, or context after having exited it.
-
C.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
D.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a8ce608190a6a4673b434945e8 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.