Triple

T4875998
Position Surface form Disambiguated ID Type / Status
Subject Łódź Voivodeship E109204 entity
Predicate namedAfter P63 FINISHED
Object city of Łódź E15327 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: city of Łódź | Statement: [Łódź Voivodeship, namedAfter, city of Łódź]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Łódź
Context triple: [Łódź Voivodeship, namedAfter, city of Łódź]
  • A. Łódź chosen
    Łódź is one of Poland’s largest cities, historically known as a major industrial and textile manufacturing center.
  • B. Lublin
    Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
  • C. Wrocław
    Wrocław is a major historic city in southwestern Poland, known for its picturesque Old Town, numerous bridges over the Oder River, and role as a cultural and academic center.
  • D. Kalisz
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • E. Opole Silesia
    Opole Silesia is a historical and cultural region in southwestern Poland, known for its mixed Polish-German heritage and centered around the city of Opole.
  • 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_69bd440e9d64819083e82cf33b4d9570 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6dba3efc8190adcf8b30490b4984 completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67fc50cc819083a475a1de914670 completed March 21, 2026, 9:42 a.m.
Created at: March 20, 2026, 1:27 p.m.