Triple

T4734610
Position Surface form Disambiguated ID Type / Status
Subject Portsmouth, England E105092 entity
Predicate hasTwinTown P919 FINISHED
Object Mikolow E107720 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: Mikolow | Statement: [Portsmouth, England, hasTwinTown, Mikolow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mikolow
Context triple: [Portsmouth, England, hasTwinTown, Mikolow]
  • A. Mikolow chosen
    Mikolow is a town in southern Poland’s Silesian Voivodeship, known for its historic center and proximity to the regional capital Katowice.
  • B. Dzyarzhynsk
    Dzyarzhynsk is a town in Belarus known for its proximity to Dzyarzhynskaya Hara, the country’s highest point.
  • C. Mogilev-Podilskyi
    Mogilev-Podilskyi is a historic city in western Ukraine near the Moldovan border, known as a regional transport and trade hub along the Dniester River.
  • D. Koserow
    Koserow is a seaside resort village on the Baltic Sea coast of the island of Usedom in northeastern Germany, known for its beaches and coastal landscapes.
  • E. Hrodna
    Hrodna is a historic city in western Belarus known for its well-preserved architecture and role as a major cultural and economic center of the region.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6467a1fc819089485b4d76e0edc4 completed March 20, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10b0b8d08190ad1cd262ee870f08 completed March 21, 2026, 3:29 a.m.
Created at: March 20, 2026, 1:19 p.m.