Triple
T2372426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 7 |
E46119
|
entity |
| Predicate | crewHealthIssue |
P4720
|
FINISHED |
| Object | head colds among all three astronauts |
—
|
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: head colds among all three astronauts | Statement: [Apollo 7, crewHealthIssue, head colds among all three astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewHealthIssue Context triple: [Apollo 7, crewHealthIssue, head colds among all three astronauts]
-
A.
crewFatality
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
B.
rescueCasualties
Indicates performing actions to locate, assist, and remove injured or endangered individuals from a hazardous or emergency situation.
-
C.
crewOutcome
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
-
D.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
E.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.