Triple
T33233273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yastreb |
E850756
|
entity |
| Predicate | associatedWithCosmonaut |
P91751
|
FINISHED |
| Object | Valery Bykovsky |
—
|
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: Valery Bykovsky | Statement: [Yastreb, associatedWithCosmonaut, Valery Bykovsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCosmonaut Context triple: [Yastreb, associatedWithCosmonaut, Valery Bykovsky]
-
A.
associatedWithAstronaut
chosen
Indicates a relationship in which an entity has a connection, link, or involvement with an astronaut.
-
B.
associatedWithSpacecraft
Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
-
C.
isAstronautOf
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
-
D.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
E.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:31 a.m.