Triple

T27735983
Position Surface form Disambiguated ID Type / Status
Subject ThreadAbortException E697528 entity
Predicate isUncommonIn P19183 FINISHED
Object asynchronous programming with async/await 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: asynchronous programming with async/await | Statement: [ThreadAbortException, isUncommonIn, asynchronous programming with async/await]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUncommonIn
Context triple: [ThreadAbortException, isUncommonIn, asynchronous programming with async/await]
  • A. isLessCommonThan chosen
    Indicates that one item occurs, appears, or is observed less frequently than another item.
  • B. moreCommonIn
    Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
  • C. isLessCommonSince
    Indicates that the frequency or prevalence of one entity has decreased relative to another entity or to its own past occurrence from a specified point in time.
  • D. commonness
    Indicates how frequently or typically something occurs or is found relative to other things.
  • E. isRareTypeOf
    Indicates that one entity is an uncommon or infrequently occurring subtype or category of another entity.
  • 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_69f636a088b8819081e34d416b28cdac 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.