Triple
T34339046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delicate Sound of Thunder |
E881231
|
entity |
| Predicate | playedInSpaceBy |
P91751
|
FINISHED |
| Object | Soviet cosmonauts |
—
|
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: Soviet cosmonauts | Statement: [Delicate Sound of Thunder, playedInSpaceBy, Soviet cosmonauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInSpaceBy Context triple: [Delicate Sound of Thunder, playedInSpaceBy, Soviet cosmonauts]
-
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.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
C.
hasFlownInSpace
Indicates that the subject has traveled beyond Earth's atmosphere into outer space.
-
D.
locatedInSpace
Indicates that one entity exists or is positioned within a specific region or area of physical space relative to another.
-
E.
associatedWithAstronaut
chosen
Indicates a relationship in which an entity has a connection, link, or involvement with an astronaut.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:58 a.m.