Triple
T34507282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 13 |
E885921
|
entity |
| Predicate | oxygenTankExplosionDate |
P12735
|
FINISHED |
| Object | 1970-04-14 |
—
|
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: 1970-04-14 | Statement: [Apollo 13, oxygenTankExplosionDate, 1970-04-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxygenTankExplosionDate Context triple: [Apollo 13, oxygenTankExplosionDate, 1970-04-14]
-
A.
explosionDateApprox
Indicates that an explosion occurred on or around a specified date, where the exact date is not known or is only approximate.
-
B.
hydrogenExplosionDate
Indicates the date on which a hydrogen explosion occurred or is scheduled to occur.
-
C.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
D.
missionAccidentDate
chosen
Indicates the date on which an accident occurred during or in relation to a mission.
-
E.
laterBlownUpTo
Indicates that one entity is subsequently destroyed or blown up at a later time relative to another referenced event or state.
- 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_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:01 a.m.