Triple

T4072142
Position Surface form Disambiguated ID Type / Status
Subject Brisbane Roar FC E86671 entity
Predicate shortName P43 FINISHED
Object Brisbane Roar E86671 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: Brisbane Roar | Statement: [Brisbane Roar FC, shortName, Brisbane Roar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brisbane Roar
Context triple: [Brisbane Roar FC, shortName, Brisbane Roar]
  • A. Brisbane Roar FC chosen
    Brisbane Roar FC is a professional Australian soccer club based in Brisbane that competes in the A-League Men.
  • B. Adelaide United FC
    Adelaide United FC is a professional soccer club based in Adelaide, South Australia, that competes in the A-League Men.
  • C. Sydney FC
    Sydney FC is a professional Australian soccer club based in Sydney that competes in the A-League Men and is one of the country's most successful and popular football teams.
  • D. Melbourne City FC
    Melbourne City FC is a professional Australian soccer club based in Melbourne that competes in the A-League Men and is part of the global City Football Group network.
  • E. Perth Glory FC
    Perth Glory FC is a professional soccer club based in Perth, Western Australia, competing in the A-League Men and known as one of the league’s historically prominent teams.
  • 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_69aed93ebe448190a1f1686e28740ac9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc20ed788190bd935082a348a05d completed March 9, 2026, 4:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69b562b99e84819085e1616fb9a61465 completed March 14, 2026, 1:29 p.m.
Created at: March 9, 2026, 3:38 p.m.