Triple
T34507538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquarius |
E885926
|
entity |
| Predicate | missionEvent |
P73551
|
FINISHED |
| Object | used after oxygen tank explosion in Apollo 13 service module |
—
|
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: used after oxygen tank explosion in Apollo 13 service module | Statement: [Aquarius, missionEvent, used after oxygen tank explosion in Apollo 13 service module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionEvent Context triple: [Aquarius, missionEvent, used after oxygen tank explosion in Apollo 13 service module]
-
A.
missionDuringIncident
Indicates that a mission or operation took place concurrently with, or in the context of, a specific incident.
-
B.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
C.
expeditionEvent
chosen
Indicates an event or occurrence that takes place as part of, or in direct connection with, an expedition.
-
D.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
E.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 2:01 a.m.