Triple
T33233286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yastreb |
E850756
|
entity |
| Predicate | cosmonautRole |
P173483
|
FINISHED |
| Object | pilot |
—
|
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: pilot | Statement: [Yastreb, cosmonautRole, pilot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmonautRole Context triple: [Yastreb, cosmonautRole, pilot]
-
A.
spaceShuttleRole
Indicates the specific function or duty an entity has in relation to a space shuttle (e.g., its operational, crew, or mission role).
-
B.
cosmonautName
Indicates that the predicate specifies the personal name associated with a given cosmonaut.
-
C.
crewRole_SergeiKrikalev
Indicates that there is a specified crew role or position associated with Sergei Krikalev within a particular mission or crew context.
-
D.
missionCrewRole
chosen
Indicates the specific role or function an individual holds as a member of a mission’s crew.
-
E.
astronaut
Indicates that an entity performs the role or activity of traveling and working in space as part of space missions.
- 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_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.