Triple

T10634472
Position Surface form Disambiguated ID Type / Status
Subject Bergkamen E250540 entity
Predicate hasSubdivision P747 FINISHED
Object Heil E876459 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: Heil | Statement: [Bergkamen, hasSubdivision, Heil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heil
Context triple: [Bergkamen, hasSubdivision, Heil]
  • A. Heil chosen
    Heil is a former municipality in Germany that was incorporated into the town of Bergkamen through an administrative merger.
  • B. Hein
    Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
  • C. Hille
    Hille is a surname and place name that appears as a variant form of "Hill" in certain linguistic or regional contexts.
  • D. Hansi
    Hansi is a historic town in the Hisar district of Haryana, India, known for its ancient forts and archaeological significance.
  • E. Heriz
    Heriz is a renowned carpet-weaving region in northwestern Iran, famous for its durable hand-knotted rugs featuring bold geometric medallion designs.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dfab47bc819086684edc1b6dce74 completed April 8, 2026, 11:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a3e0e1481909c277be4c12b46ea completed April 10, 2026, 10:31 p.m.
Created at: April 8, 2026, 9:03 p.m.