Triple
T27735971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThreadAbortException |
E697528
|
entity |
| Predicate | isDiscouragedIn |
P96795
|
FINISHED |
| Object | .NET Core |
—
|
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 Core | Statement: [ThreadAbortException, isDiscouragedIn, .NET Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiscouragedIn Context triple: [ThreadAbortException, isDiscouragedIn, .NET Core]
-
A.
isEncouragedInContext
Indicates that an action, behavior, or state is positively promoted, supported, or recommended within a specific context or situation.
-
B.
discouragedUsageReason
Indicates the reason why a particular usage, action, or practice is considered discouraged.
-
C.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
D.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
E.
accessDiscouragedFor
chosen
Indicates that access to a particular entity is discouraged or not recommended for another entity, even if it may still be technically possible.
- 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.