Triple
T27735976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadAbortException |
E697528
|
entity |
| Predicate | isNotThrownBy |
P119089
|
FINISHED |
| Object | Task cancellation APIs |
—
|
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: Task cancellation APIs | Statement: [ThreadAbortException, isNotThrownBy, Task cancellation APIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotThrownBy Context triple: [ThreadAbortException, isNotThrownBy, Task cancellation APIs]
-
A.
canBeThrownBy
chosen
Indicates that one entity is capable of being thrown or launched by another entity.
-
B.
doesNotProvideExceptionFor
Indicates that one party or rule fails to grant an exemption, special case, or exclusion to another party or situation.
-
C.
canBeThrown
Indicates that an entity is suitable or able to be propelled through the air by being thrown.
-
D.
isNotCausedBy
Indicates that one entity does not serve as the cause or origin of another entity, event, or condition.
-
E.
wasThrownFrom
Indicates that an entity was propelled away or ejected from another entity, typically by a forceful or intentional throwing action.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 3:12 p.m.