Triple
T36722360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 8 |
E907100
|
entity |
| Predicate | reentryModuleLanding |
P54852
|
FINISHED |
| Object | Kazakhstan |
—
|
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: Kazakhstan | Statement: [Soyuz 8, reentryModuleLanding, Kazakhstan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryModuleLanding Context triple: [Soyuz 8, reentryModuleLanding, Kazakhstan]
-
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
Indicates the process or capability of safely recovering an object or vehicle after it reenters an atmosphere from space or high-altitude flight.
-
C.
reentryCapsuleLandingCountry
chosen
Indicates the country where a spacecraft’s reentry capsule lands or is intended to land.
-
D.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
E.
landingRecovery
Indicates the process or method by which something is retrieved or secured after it has landed.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.