Triple
T34714193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astronaut Group 20 |
E1000727
|
entity |
| Predicate | spacecraftFlownByMembers |
P143810
|
FINISHED |
| Object | Soyuz |
—
|
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: Soyuz | Statement: [NASA Astronaut Group 20, spacecraftFlownByMembers, Soyuz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftFlownByMembers Context triple: [NASA Astronaut Group 20, spacecraftFlownByMembers, Soyuz]
-
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.
spaceMissionsFlown
Indicates the number or specific instances of space missions that an entity has participated in or carried out.
-
C.
associatedWithAstronaut
Indicates a relationship in which an entity has a connection, link, or involvement with an astronaut.
-
D.
notableAstronautUser
Indicates that the user has a notable or distinguished status specifically as an astronaut.
-
E.
spaceflightVehicleFlown
chosen
Indicates that a particular spaceflight vehicle has been operated or flown by a specific agent (such as a person, crew, or organization).
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.