Triple
T34507299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 13 |
E885921
|
entity |
| Predicate | serviceModuleJettisonTime |
P94493
|
FINISHED |
| Object | just before Earth reentry on 1970-04-17 |
—
|
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: just before Earth reentry on 1970-04-17 | Statement: [Apollo 13, serviceModuleJettisonTime, just before Earth reentry on 1970-04-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceModuleJettisonTime Context triple: [Apollo 13, serviceModuleJettisonTime, just before Earth reentry on 1970-04-17]
-
A.
serviceModuleJettisonDate
chosen
Indicates the date on which a service module is detached or jettisoned from the main vehicle or system.
-
B.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
C.
serviceEnded
Indicates that a previously active service or service relationship has come to an end.
-
D.
hasServiceTime
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
E.
serviceModuleFunction
Indicates that a function is provided or performed by a specific service module within a system.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.