Triple

T4244954
Position Surface form Disambiguated ID Type / Status
Subject Union of Polish Metropolises E95505 entity
Predicate hasMember P10 FINISHED
Object Rybnik E351435 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: Rybnik | Statement: [Union of Polish Metropolises, hasMember, Rybnik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rybnik
Context triple: [Union of Polish Metropolises, hasMember, Rybnik]
  • A. Rybnik chosen
    Rybnik is a significant industrial and cultural city in the Silesian region of southern Poland, known for its coal mining heritage and regional economic importance.
  • B. Dąbie
    Dąbie is a small town in central Poland, located in the Łódź Voivodeship along the Ner River.
  • C. Skawina
    Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
  • D. Rybi Potok
    Rybi Potok is a mountain stream in the Tatra Mountains of southern Poland that drains the waters of the popular alpine lake Morskie Oko.
  • E. Bílina
    Bílina is a river in the Czech Republic that flows through the Ústí nad Labem Region and is known for passing through several industrial and mining areas.
  • 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_69b3453d91548190b4d4ef8fe52aa2ac completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e8c42e88190b309a1ef7f6529ac completed March 12, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c710c2f081908b9be1da2bdf1b43 completed March 14, 2026, 8:37 p.m.
Created at: March 12, 2026, 11:05 p.m.