Triple

T19750184
Position Surface form Disambiguated ID Type / Status
Subject Function Compute E474353 entity
Predicate supports P516 FINISHED
Object CDN events 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: CDN events | Statement: [Function Compute, supports, CDN events]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CDN events
Context triple: [Function Compute, supports, CDN events]
  • A. CDN
    CDN is the ICAO airline designator formerly assigned to Canadian Airlines, a major now-defunct Canadian carrier.
  • B. HCDN
    HCDN is the commonly used abbreviation for the Chamber of Deputies, the lower house of Argentina’s National Congress.
  • C. Alibaba Cloud CDN chosen
    Alibaba Cloud CDN is a content delivery network service that accelerates the distribution of web content globally by caching and delivering data from edge nodes closer to end users.
  • D. Currant Events
    Currant Events is a fantasy novel in Piers Anthony’s long-running Xanth series, known for its heavy use of puns and whimsical magical adventures.
  • E. Server-Sent Events
    Server-Sent Events is a web technology that enables servers to push real-time, one-way event updates to clients over a single long-lived HTTP connection.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6529875688190952af476aa5be492 completed April 20, 2026, 4:21 p.m.
Created at: April 10, 2026, 1:47 p.m.