Triple
T27549106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-3 |
E695441
|
entity |
| Predicate | reentryModuleReturned |
P92794
|
FINISHED |
| Object | to Earth |
—
|
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: to Earth | Statement: [Soyuz TMA-3, reentryModuleReturned, to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryModuleReturned Context triple: [Soyuz TMA-3, reentryModuleReturned, to Earth]
-
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.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
C.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
D.
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.
-
E.
reentryCause
Indicates the factor, event, or condition that led to or triggered a reentry.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f877c988190928b6321c1f3f8f2 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:34 p.m.