Triple

T10814553
Position Surface form Disambiguated ID Type / Status
Subject TPS Turku E255189 entity
Predicate governingBody P46 FINISHED
Object Turun Palloseura ry E887550 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: Turun Palloseura ry | Statement: [TPS Turku, governingBody, Turun Palloseura ry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turun Palloseura ry
Context triple: [TPS Turku, governingBody, Turun Palloseura ry]
  • A. Turun Palloseura chosen
    Turun Palloseura is a Finnish sports club from Turku best known for its professional football team competing in the national league system.
  • B. Imatran Pallo-Veikot
    Imatran Pallo-Veikot is a Finnish sports club best known for its football activities, based in the town of Imatra.
  • C. Vaasan Palloseura
    Vaasan Palloseura is a Finnish professional football club based in the city of Vaasa.
  • D. Vaasan Sport
    Vaasan Sport is a Finnish professional ice hockey club based in the city of Vaasa that competes in the country’s top leagues.
  • E. HIFK Helsinki
    HIFK Helsinki is a prominent professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and traditional teams in the Liiga.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d733ece4488190b553a66c4b5188bc completed April 9, 2026, 5:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69deb0f9e3a081908163b398d845deeb completed April 14, 2026, 9:26 p.m.
Created at: April 8, 2026, 9:18 p.m.