Triple
T11108765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Servicing Mission 4 |
E262699
|
entity |
| Predicate | wasInitiallyCancelled |
P97309
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hubble Servicing Mission 4, wasInitiallyCancelled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInitiallyCancelled Context triple: [Hubble Servicing Mission 4, wasInitiallyCancelled, true]
-
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.
isCancelled
Indicates that a planned event, action, or arrangement has been officially terminated and will no longer take place.
-
D.
cancellationAnnouncedOn
Indicates that the cancellation of something (e.g., an event, service, or agreement) was publicly announced on a specific date or time.
-
E.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a67d10c8190815d4c27d55270e8 |
completed | April 9, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.