Triple
T21130296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OFT |
E520666
|
entity |
| Predicate | anomaly |
P67395
|
FINISHED |
| Object | mission elapsed timer error |
—
|
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: mission elapsed timer error | Statement: [OFT, anomaly, mission elapsed timer error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anomaly Context triple: [OFT, anomaly, mission elapsed timer error]
-
A.
hasAnomaly
chosen
Indicates that an entity exhibits, contains, or is associated with an irregular, abnormal, or unexpected condition or feature.
-
B.
launchAnomaly
Indicates that an unexpected or abnormal condition occurred during the launch process of a system, vehicle, or mission.
-
C.
geographicalAnomaly
Indicates a relationship where a location exhibits unusual or irregular geographical features or conditions compared to its surrounding area.
-
D.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
E.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723556ec08190a2ade96c76f9cec7 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.