Triple
T19177330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAL 9000 |
E469472
|
entity |
| Predicate | malfunctions |
P95465
|
FINISHED |
| Object | during Jupiter mission |
—
|
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: during Jupiter mission | Statement: [HAL 9000, malfunctions, during Jupiter mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: malfunctions Context triple: [HAL 9000, malfunctions, during Jupiter mission]
-
A.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
B.
defect
chosen
Indicates that an entity has a fault, imperfection, or malfunction that causes it to deviate from an expected standard or proper functioning.
-
C.
engineFailure
Indicates that an engine has malfunctioned or ceased to operate as intended.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.