Triple

T3794399
Position Surface form Disambiguated ID Type / Status
Subject Górnik Łęczna E89733 entity
Predicate locatedIn P40 FINISHED
Object Łęczna E411025 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: Łęczna | Statement: [Górnik Łęczna, locatedIn, Łęczna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Łęczna
Context triple: [Górnik Łęczna, locatedIn, Łęczna]
  • A. Łęczna chosen
    Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
  • B. Oleśnica
    Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
  • C. Szczawnica
    Szczawnica is a Polish spa and tourist town in southern Lesser Poland, known for its mineral springs, health resorts, and scenic location in the Pieniny region near the Dunajec River.
  • D. Ojców
    Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
  • E. Łeba
    Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee79db2e88190b3aa2b8e8d885e19 completed March 9, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5e4ca9164819088b261d148e0d379 completed March 14, 2026, 10:44 p.m.
Created at: March 9, 2026, 3:15 p.m.