Triple

T22960653
Position Surface form Disambiguated ID Type / Status
Subject Lokeren E570885 entity
Predicate sportsTeam P330 FINISHED
Object KSC Lokeren-Temse 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: KSC Lokeren-Temse | Statement: [Lokeren, sportsTeam, KSC Lokeren-Temse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KSC Lokeren-Temse
Context triple: [Lokeren, sportsTeam, KSC Lokeren-Temse]
  • A. K.S.C. Lokeren Oost-Vlaanderen chosen
    K.S.C. Lokeren Oost-Vlaanderen was a Belgian professional football club based in Lokeren, known for competing in the country’s top division and featuring several notable international players.
  • B. Lokeren
    Lokeren is a Belgian city known for its textile and food industries, located in the province of East Flanders between Ghent and Antwerp.
  • C. KRC Genk
    KRC Genk is a Belgian professional football club known for developing top talents, including Kevin De Bruyne, and competing in the country’s top division.
  • D. Beerschot A.C.
    Beerschot A.C. was a historic Belgian football club from Antwerp, known for its passionate fanbase and intense local derby rivalry with Royal Antwerp F.C.
  • E. Zulte
    Zulte is a municipality in the Belgian province of East Flanders.
  • 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_69e245b212a88190b5259caf51606084 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181f494348190a24f09d3495b0950 completed April 29, 2026, 3:58 a.m.
Created at: April 17, 2026, 3:47 p.m.