Triple

T10939841
Position Surface form Disambiguated ID Type / Status
Subject Recklinghausen E258438 entity
Predicate hasTwinTown P919 FINISHED
Object Bytom E104306 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: Bytom | Statement: [Recklinghausen, hasTwinTown, Bytom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bytom
Context triple: [Recklinghausen, hasTwinTown, Bytom]
  • A. Bytom chosen
    Bytom is an industrial city in southern Poland’s Silesian region, known for its mining heritage and historical urban architecture.
  • B. Borotiam
    Borotiam is a village located on the atoll of Abaiang in the island nation of Kiribati in the central Pacific Ocean.
  • C. Barabai
    Barabai is a town and administrative center in Hulu Sungai Tengah Regency on the island of Borneo in Indonesia’s South Kalimantan province.
  • D. Bori
    Bori is a prominent urban center in Nigeria’s Rivers State, serving as an important commercial and administrative hub for the surrounding region.
  • E. Balya
    Balya is a small town and district in western Turkey known historically for its mining activities and rural character.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770c1389881909341170984211810 completed April 9, 2026, 9:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69e23c0e940081908c84ea4cf3b877fc completed April 17, 2026, 1:56 p.m.
Created at: April 8, 2026, 9:23 p.m.