Triple
T27735962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadAbortException |
E697528
|
entity |
| Predicate | abortCancellationMethod |
P132848
|
FINISHED |
| Object | Thread.ResetAbort |
—
|
NE NERFINISHED |
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: Thread.ResetAbort | Statement: [ThreadAbortException, abortCancellationMethod, Thread.ResetAbort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abortCancellationMethod Context triple: [ThreadAbortException, abortCancellationMethod, Thread.ResetAbort]
-
A.
cancellationMethod
chosen
Indicates the method or process by which a previously arranged action, service, or agreement is canceled.
-
B.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
C.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
D.
cancelArgument
Indicates that one party withdraws, nullifies, or calls off a previously made argument or claim in relation to another entity.
-
E.
onCancel
Indicates that an ongoing or scheduled action, process, or request is being terminated or withdrawn before its normal completion.
- 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.