Triple
T36560956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 13 Lunar Module Aquarius |
E901834
|
entity |
| Predicate | jettisonedBefore |
P110289
|
FINISHED |
| Object | Apollo 13 Earth reentry |
—
|
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: Apollo 13 Earth reentry | Statement: [Apollo 13 Lunar Module Aquarius, jettisonedBefore, Apollo 13 Earth reentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jettisonedBefore Context triple: [Apollo 13 Lunar Module Aquarius, jettisonedBefore, Apollo 13 Earth reentry]
-
A.
jettisonEvent
chosen
Indicates an event in which an object or cargo is deliberately discarded or ejected from a vehicle, vessel, or system.
-
B.
scuttledAfter
Indicates that one entity was deliberately sunk or rendered inoperable after the occurrence or completion of another specified event or action.
-
C.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
D.
isAbandonedAtSeaBy
Indicates that one entity is deliberately left behind or deserted at sea by another entity.
-
E.
ascentStageJettisonDate
Indicates the date on which the ascent stage of a spacecraft is separated or discarded.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.