Triple
T32123685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSInternalInconsistencyException |
E820442
|
entity |
| Predicate | errorDomainType |
P43799
|
FINISHED |
| Object | exception rather than NSError |
—
|
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: exception rather than NSError | Statement: [NSInternalInconsistencyException, errorDomainType, exception rather than NSError]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorDomainType Context triple: [NSInternalInconsistencyException, errorDomainType, exception rather than NSError]
-
A.
errorType
chosen
Indicates the specific category or kind of error associated with an event, action, or entity.
-
B.
errorTypePrefix
Indicates that one entity specifies a prefix used to categorize or identify the type of an error associated with another entity.
-
C.
rejectionErrorType
Indicates the specific category or nature of the error that caused a rejection to occur.
-
D.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
E.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:29 a.m.