Triple
T32123672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSInternalInconsistencyException |
E820442
|
entity |
| Predicate | typicalEffect |
—
|
GENERATED |
| Object | application termination |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEffect Context triple: [NSInternalInconsistencyException, typicalEffect, application termination]
-
A.
traditionalEffect
Indicates the customary or historically established impact or influence that something has within a cultural or traditional context.
-
B.
effectDescription
Indicates a textual explanation of the outcome, consequence, or impact resulting from an action, event, or condition.
-
C.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
effectCategory
Indicates the general type or classification of an effect that one entity has on another or on a system.
-
E.
specialEffect
Indicates that one entity produces, applies, or is associated with a distinctive, often non-standard effect on another entity or on an event.
- F. None of above.
Provenance (1 batch)
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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:29 a.m.