Triple
T27735980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadAbortException |
E697528
|
entity |
| Predicate | isMarkedObsoleteIn |
P88270
|
FINISHED |
| Object | .NET 5+ |
—
|
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: .NET 5+ | Statement: [ThreadAbortException, isMarkedObsoleteIn, .NET 5+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarkedObsoleteIn Context triple: [ThreadAbortException, isMarkedObsoleteIn, .NET 5+]
-
A.
isObsoleteFor
Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
-
B.
hasObsolescenceReason
Indicates that an entity is associated with a specific reason explaining why it has become obsolete or is no longer in use.
-
C.
becameObsoleteWhen
Indicates that one thing lost its relevance, usefulness, or validity at the time another specified event, condition, or entity came into existence or took effect.
-
D.
isDeprecatedByPublisher
Indicates that a publisher has officially marked the referenced item as deprecated or no longer recommended for use.
-
E.
isDeprecatedIn
chosen
Indicates that a given entity is considered outdated or no longer recommended for use within a specified context, version, or time frame.
- 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:12 p.m.