Triple

T11161985
Position Surface form Disambiguated ID Type / Status
Subject Jastrzębie-Zdrój E264057 entity
Predicate hasNearbyCity P350 FINISHED
Object Żory E607773 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: Żory | Statement: [Jastrzębie-Zdrój, hasNearbyCity, Żory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Żory
Context triple: [Jastrzębie-Zdrój, hasNearbyCity, Żory]
  • A. Żory chosen
    Żory is a city in southern Poland known for its historical roots in the Silesian region and its mix of industrial and residential character.
  • B. Danzig
    Danzig is an American heavy metal band formed by singer Glenn Danzig, known for its dark, blues-influenced sound and songs like "Mother."
  • C. Serock
    Serock is a locality situated near the Western Bug River in eastern Europe.
  • D. Perekop
    Perekop is a small settlement in northern Crimea historically known for its strategic location near the narrow land connection between the Crimean Peninsula and mainland Ukraine.
  • E. Kolberg
    Kolberg is a historic Baltic Sea port city in present-day Kołobrzeg, Poland, known for its strategic military importance and spa tourism.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8832fe88190a74d81f9ed547baa completed April 9, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69e46375c61c8190939401f790cf1593 completed April 19, 2026, 5:09 a.m.
Created at: April 8, 2026, 9:29 p.m.