Triple

T15967014
Position Surface form Disambiguated ID Type / Status
Subject Antalya Stadium E387217 entity
Predicate homeStadiumOf P2696 FINISHED
Object Antalyaspor E83261 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: Antalyaspor | Statement: [Antalya Stadium, homeStadiumOf, Antalyaspor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antalyaspor
Context triple: [Antalya Stadium, homeStadiumOf, Antalyaspor]
  • A. Antalyaspor chosen
    Antalyaspor is a professional Turkish football club based in Antalya that competes in the country’s top-tier league, the Süper Lig.
  • B. Alanyaspor
    Alanyaspor is a professional Turkish football club based in Alanya that competes in the country’s top leagues and is known for its regional rivalry with Antalyaspor.
  • C. Kayserispor
    Kayserispor is a professional Turkish football club based in Kayseri that competes in the country’s top leagues.
  • D. Denizlispor
    Denizlispor is a professional Turkish football club based in the city of Denizli that competes in the national league system.
  • E. Manisaspor
    Manisaspor is a Turkish professional football club based in the city of Manisa, known for competing in the national league system and developing local talent.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e15726536881908b603e43ae1acafb completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffbe87149081909ac6129126f597c2 completed May 9, 2026, 11:08 p.m.
Created at: April 10, 2026, 4:54 a.m.