Triple

T9336483
Position Surface form Disambiguated ID Type / Status
Subject Kuyavian-Pomeranian Voivodeship E224654 entity
Predicate hasHistoricCentreIn P17588 FINISHED
Object Toruń 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: Toruń | Statement: [Kuyavian-Pomeranian Voivodeship, hasHistoricCentreIn, Toruń]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricCentreIn
Context triple: [Kuyavian-Pomeranian Voivodeship, hasHistoricCentreIn, Toruń]
  • A. isHistoricCenterOf
    Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
  • B. hasHistoricCenterStatus
    Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
  • C. isInHistoricCenterOf
    Indicates that one entity is located within the historic center area of another entity (typically a city or town).
  • D. hasMajorHistoricalCentersIn chosen
    Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
  • E. hasHistoricCenterShape
    Indicates the geometric form or configuration that characterizes the historic center of a place or settlement.
  • F. None of above.

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_69ca84286fcc81909f6e7fd7a7e862a2 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd37f161e481908e23c1ec7e5fcf97 completed April 1, 2026, 3:21 p.m.
PD Predicate disambiguation batch_69cc7a66aef08190b8d668cff5b04f5f completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:40 p.m.