Triple
T27735989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadAbortException |
E697528
|
entity |
| Predicate | isNotIntendedFor |
P99717
|
FINISHED |
| Object | normal application flow control |
—
|
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: normal application flow control | Statement: [ThreadAbortException, isNotIntendedFor, normal application flow control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotIntendedFor Context triple: [ThreadAbortException, isNotIntendedFor, normal application flow control]
-
A.
notPrimarilyIntendedFor
chosen
Indicates that something is used or occurs in a way that is not its main or original purpose or target.
-
B.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
C.
isNotIndicatedFor
Indicates that a treatment, action, or option is not recommended or appropriate for a particular condition, situation, or entity.
-
D.
isIntendedToSupport
Indicates that one entity is designed or purposed to provide assistance, reinforcement, or backing to another entity or activity.
-
E.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 3:12 p.m.