Triple
T28030255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-13 |
E708244
|
entity |
| Predicate | carriedVisitingResearchCosmonaut |
P64491
|
FINISHED |
| Object | Toktar Aubakirov |
E1791438
|
NE 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: Toktar Aubakirov | Statement: [Soyuz TM-13, carriedVisitingResearchCosmonaut, Toktar Aubakirov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedVisitingResearchCosmonaut Context triple: [Soyuz TM-13, carriedVisitingResearchCosmonaut, Toktar Aubakirov]
-
A.
researchCosmonaut
Indicates that one entity conducts research on, studies, or investigates a cosmonaut.
-
B.
cosmonautName
Indicates that the predicate specifies the personal name associated with a given cosmonaut.
-
C.
notableCosmonaut
Indicates that the subject is a cosmonaut who is distinguished or well-known for their role, achievements, or significance in spaceflight.
-
D.
aboardSpacecraft
chosen
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
E.
cargoSpacecraftVisited
Indicates that a cargo spacecraft has made a visit to a particular location or object.
- F. None of above.
Provenance (4 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15c90135688190b3206da0edafa051 |
completed | May 26, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 8:15 p.m.