Triple

T6974658
Position Surface form Disambiguated ID Type / Status
Subject Telkom Knockout E161686 entity
Predicate mainSponsor P737 FINISHED
Object Telkom E633662 NE 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: Telkom | Statement: [Telkom Knockout, mainSponsor, Telkom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telkom
Context triple: [Telkom Knockout, mainSponsor, Telkom]
  • A. Telkom chosen
    Telkom is a major South African telecommunications company that provides fixed-line, mobile, and data services across the country.
  • B. Pacific Telesis
    Pacific Telesis was a regional telecommunications company formed after the breakup of AT&T, serving as one of the Baby Bells providing local telephone and related services in the western United States.
  • C. Telenor
    Telenor is a major Norwegian telecommunications company that provides mobile, broadband, and digital services across Scandinavia and multiple international markets.
  • D. Telico
    Telico is a small unincorporated community located in Ellis County, Texas.
  • E. Opal Telecom
    Opal Telecom was a UK-based telecommunications provider that became part of TalkTalk’s business services operations following its acquisition.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68854a0d88190bc0bf82263f1afce completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6db3bda908190a10a91dc8d043ef1 completed March 27, 2026, 7:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a0735548190a406387c929cca07 completed March 28, 2026, 5:41 a.m.
Created at: March 27, 2026, 2:30 p.m.