Triple
T32150173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSInvalidArgumentException |
E821135
|
entity |
| Predicate | isFatalByDefault |
P173637
|
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: [NSInvalidArgumentException, isFatalByDefault, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFatalByDefault Context triple: [NSInvalidArgumentException, isFatalByDefault, true]
-
A.
isDefaultFor
Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
-
B.
hasCriticalBehaviorDescribedBy
Indicates that an entity’s critical or essential behavior is specified or characterized by another entity (such as a description, model, or specification).
-
C.
diesFor
Indicates that one entity sacrifices its life for the sake, benefit, or protection of another entity.
-
D.
isKilledTo
Indicates that one entity is killed as a consequence or objective of an action performed by another entity.
-
E.
isPermissive
Indicates that an entity allows, tolerates, or does not restrict a particular action, behavior, or condition.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9e7cb088190926d6a5c524e5eab |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:31 a.m.