Triple
T19442191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir-18 |
E486376
|
entity |
| Predicate | includedCosmonaut |
P91751
|
FINISHED |
| Object | Vladimir Dezhurov |
—
|
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: Vladimir Dezhurov | Statement: [Mir-18, includedCosmonaut, Vladimir Dezhurov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedCosmonaut Context triple: [Mir-18, includedCosmonaut, Vladimir Dezhurov]
-
A.
isAstronautOf
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
-
B.
associatedWithAstronaut
chosen
Indicates a relationship in which an entity has a connection, link, or involvement with an astronaut.
-
C.
cosmonautName
Indicates that the predicate specifies the personal name associated with a given cosmonaut.
-
D.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
E.
selectedAsAstronaut
Indicates that an individual has been formally chosen to serve as an astronaut, typically through an official selection process.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63365343081908683c29f6c4c194b |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.