Triple

T20492223
Position Surface form Disambiguated ID Type / Status
Subject İzmit E502772 entity
Predicate hasHistoricalName P2834 FINISHED
Object Ismid 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: Ismid | Statement: [İzmit, hasHistoricalName, Ismid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ismid
Context triple: [İzmit, hasHistoricalName, Ismid]
  • A. Ismid chosen
    Ismid is a historical name for the Turkish city of İzmit, an important settlement in northwestern Anatolia with roots dating back to antiquity.
  • B. Meliden
    Meliden is a village in Denbighshire, North Wales, situated inland from the coastal town of Prestatyn.
  • C. Heiden
    Heiden is a municipality in the Swiss canton of Appenzell Ausserrhoden, known as the place where Red Cross founder Henry Dunant spent his final years and died.
  • D. Heiden
    Heiden is a municipality in the Borken district of North Rhine-Westphalia in western Germany, known for its rural character and local cultural traditions.
  • E. Heiden
    Heiden is the central hall of worship within Japan’s Itsukushima Shrine, used for Shinto religious ceremonies and offerings.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cba5b708190bef437acf6321b81 completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.