Triple

T14896878
Position Surface form Disambiguated ID Type / Status
Subject Będzin Castle E359900 entity
Predicate locatedIn P40 FINISHED
Object Będzin NE NERFINISHED

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: Będzin | Statement: [Będzin Castle, locatedIn, Będzin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Będzin
Context triple: [Będzin Castle, locatedIn, Będzin]
  • A. Będzin chosen
    Będzin is a historic town in southern Poland’s Silesian Voivodeship, known for its medieval castle and long-standing role as a regional urban center.
  • B. Bielany
    Bielany is a northern district of Warsaw, Poland, known for its residential neighborhoods, green spaces, and connection to the city center via the Warsaw Metro.
  • C. Brzesko
    Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
  • D. Wojkowice
    Wojkowice is a small town in southern Poland’s Silesian Voivodeship, situated in the industrial and urbanized Upper Silesian region.
  • E. City of Będzin
    The City of Będzin is a historic urban center in southern Poland, known for its medieval heritage, including a prominent castle, and its role in the Silesian region’s cultural and industrial history.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded6070b248190be8f4f91a0c0b1f3 completed April 15, 2026, 12:04 a.m.
Created at: April 10, 2026, 2:11 a.m.