Triple
T23462492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Randolph |
E569017
|
entity |
| Predicate | recoveredAstronaut |
P142317
|
FINISHED |
| Object | Virgil I. Grissom |
—
|
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: Virgil I. Grissom | Statement: [USS Randolph, recoveredAstronaut, Virgil I. Grissom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveredAstronaut Context triple: [USS Randolph, recoveredAstronaut, Virgil I. Grissom]
-
A.
returnedAstronaut
chosen
Indicates that an astronaut has come back from a mission, typically returning from space to Earth.
-
B.
isAstronautOf
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
-
C.
astronautSurvived
Indicates that an astronaut remained alive after a specific event, mission, or hazardous situation.
-
D.
notableCosmonaut
Indicates that the subject is a cosmonaut who is distinguished or well-known for their role, achievements, or significance in spaceflight.
-
E.
associatedSpaceShuttleAstronauts
Indicates that there is an association or relevant connection between a given subject and one or more space shuttle astronauts.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69cf7c48190b4d44e500f955b99 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.