Triple
T27733761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Threading.Thread |
E697485
|
entity |
| Predicate | AbortStatus |
P148356
|
FINISHED |
| Object | Abort() is obsolete in .NET Core and later |
—
|
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: Abort() is obsolete in .NET Core and later | Statement: [System.Threading.Thread, AbortStatus, Abort() is obsolete in .NET Core and later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AbortStatus Context triple: [System.Threading.Thread, AbortStatus, Abort() is obsolete in .NET Core and later]
-
A.
abortModeUsed
chosen
Indicates that an operation, process, or procedure was carried out using an abort or emergency-termination mode.
-
B.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
C.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
-
D.
statusAtInterruption
Indicates the specific state or condition something was in at the moment it was interrupted.
-
E.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
- 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_69f6369e16a08190853fdd8ac05800f6 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.