Triple

T20383
Position Surface form Disambiguated ID Type / Status
Subject Fellow of the Association for Computing Machinery E404 entity
Predicate targetCommunity P1113 FINISHED
Object global computing community 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: global computing community | Statement: [Fellow of the Association for Computing Machinery, targetCommunity, global computing community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetCommunity
Context triple: [Fellow of the Association for Computing Machinery, targetCommunity, global computing community]
  • A. targetMarket
    Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
  • B. target
    Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
  • C. notableCommunity chosen
    Indicates that an entity is a particularly prominent or significant member of a given community.
  • D. primaryTarget
    Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
  • E. supportedPopulation
    Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
  • 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_69a240778d288190815c0052ebbbcc91 completed Feb. 28, 2026, 1:10 a.m.
NER Named-entity recognition batch_69a246f7bd30819085f751c41f6f029e completed Feb. 28, 2026, 1:37 a.m.
PD Predicate disambiguation batch_69a246526f5881909bc2a46e978bd082 completed Feb. 28, 2026, 1:35 a.m.
Created at: Feb. 28, 2026, 1:14 a.m.