Triple

T20890021
Position Surface form Disambiguated ID Type / Status
Subject Sydney Thunder E514382 entity
Predicate rivalTeam P16339 FINISHED
Object Sydney Sixers 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: Sydney Sixers | Statement: [Sydney Thunder, rivalTeam, Sydney Sixers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sydney Sixers
Context triple: [Sydney Thunder, rivalTeam, Sydney Sixers]
  • A. Sydney Sixers chosen
    Sydney Sixers are a professional Twenty20 cricket team based in Sydney that competes in Australia’s Big Bash League.
  • B. Perth Scorchers
    Perth Scorchers are a professional Twenty20 cricket team based in Perth, Western Australia, competing in Australia’s Big Bash League.
  • C. Sydney Stars
    Sydney Stars was a professional rugby union team based in Sydney that competed in Australia's National Rugby Championship.
  • D. Sydney Thunder
    Sydney Thunder is a professional Twenty20 cricket franchise based in Western Sydney that competes in Australia’s Big Bash League.
  • E. Brisbane Heat
    Brisbane Heat is a professional Twenty20 cricket team based in Brisbane that competes in Australia's Big Bash League.
  • 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_69e0b4f7ebe48190952a85547a0f31a1 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6d05d591481908c9c999db76760fc completed April 21, 2026, 1:18 a.m.
Created at: April 16, 2026, 12:46 p.m.