Triple

T8006044
Position Surface form Disambiguated ID Type / Status
Subject KRC Genk E186365 entity
Predicate shortName P43 FINISHED
Object Racing Genk E186365 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: Racing Genk | Statement: [KRC Genk, shortName, Racing Genk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Racing Genk
Context triple: [KRC Genk, shortName, Racing Genk]
  • A. Racing Mechelen
    Racing Mechelen is a Belgian football club based in the city of Mechelen, known for its historic presence in the national leagues.
  • B. KRC Genk chosen
    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.
  • C. KAA Gent
    KAA Gent is a Belgian professional football club based in Ghent, known for competing in the country’s top division and developing notable players such as Kevin De Bruyne.
  • D. Lokeren
    Lokeren is a Belgian city known for its textile and food industries, located in the province of East Flanders between Ghent and Antwerp.
  • E. KV Mechelen
    KV Mechelen is a Belgian professional football club known for competing in the country’s top leagues and for its passionate local fan base.
  • 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3cf72fc08190aa78b97c1ab92f90 completed March 31, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc5697ac9081909fe7ca06d0c3ef38 completed March 31, 2026, 11:19 p.m.
Created at: March 30, 2026, 5:18 p.m.