Triple
T15556694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 19 |
E370887
|
entity |
| Predicate | canceledBefore |
P119165
|
FINISHED |
| Object | launch |
—
|
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: launch | Statement: [Apollo 19, canceledBefore, launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canceledBefore Context triple: [Apollo 19, canceledBefore, launch]
-
A.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
-
B.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
C.
wasInitiallyCancelled
Indicates that an event, action, or request was first cancelled at some point, regardless of its later status.
-
D.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
E.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
- F. None of above. chosen
Provenance (4 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:09 a.m.