Triple

T16495668
Position Surface form Disambiguated ID Type / Status
Subject Łódź derby E400676 entity
Predicate hasLocalName P6353 FINISHED
Object Derby Łodzi E400676 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: Derby Łodzi | Statement: [Łódź derby, hasLocalName, Derby Łodzi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Derby Łodzi
Context triple: [Łódź derby, hasLocalName, Derby Łodzi]
  • A. Derby Poznania
    Derby Poznania is the local football derby in Poznań, Poland, contested between city rivals Lech Poznań and Warta Poznań.
  • B. Derby Trójmiasta
    Derby Trójmiasta is a Polish football rivalry match between clubs from the Tricity metropolitan area of Gdańsk, Gdynia, and Sopot.
  • C. Łódź derby chosen
    The Łódź derby is the fiercely contested football rivalry between the two major clubs from the Polish city of Łódź, Widzew Łódź and ŁKS Łódź.
  • D. Stadion Widzewa Łódź
    Stadion Widzewa Łódź is a modern football stadium in Łódź, Poland, primarily used for professional matches and events involving the Widzew Łódź football club.
  • E. Tricity Derby
    Tricity Derby is a fiercely contested Polish football rivalry match between clubs from the Tricity metropolitan area on the Baltic coast.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e332c1c8190888a042d0192233a completed April 18, 2026, 7:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a005828849481909e95c5822ed6f74d completed May 10, 2026, 10:04 a.m.
Created at: April 10, 2026, 5:14 a.m.