Triple

T8128895
Position Surface form Disambiguated ID Type / Status
Subject Temple Challenge Cup E189805 entity
Predicate namedAfter P63 FINISHED
Object Temple E104190 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: Temple | Statement: [Temple Challenge Cup, namedAfter, Temple]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Temple
Context triple: [Temple Challenge Cup, namedAfter, Temple]
  • A. Temple chosen
    Temple is a historic legal district in central London, renowned for housing the Inns of Court and many barristers’ chambers.
  • B. Temple
    Temple is a surname of English origin borne by various notable individuals across fields such as politics, sports, and the arts.
  • C. Temple
    Temple is the athletic program of Temple University, best known for its NCAA Division I sports teams, particularly in basketball and football.
  • D. Temple
    Temple is a mid-sized city in central Texas known as a regional medical and transportation hub.
  • E. The Temple
    The Temple is a large, spiritually themed art installation at Burning Man that serves as a communal space for reflection, mourning, and symbolic release before being ceremonially burned.
  • 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_69ca82bcb4848190a9a9d036ad768642 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb439190d88190aa614445c7479353 completed March 31, 2026, 3:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc947303f881908e16af664fb74dc8 completed April 1, 2026, 3:43 a.m.
Created at: March 30, 2026, 5:34 p.m.