Triple

T32911518
Position Surface form Disambiguated ID Type / Status
Subject Municipality of Slagelse E841888 entity
Predicate containsHistoricMarketTown P17485 FINISHED
Object Slagelse 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: Slagelse | Statement: [Municipality of Slagelse, containsHistoricMarketTown, Slagelse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsHistoricMarketTown
Context triple: [Municipality of Slagelse, containsHistoricMarketTown, Slagelse]
  • A. containsHistoricTown
    Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
  • B. hasMarketTownHistory chosen
    Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
  • C. historicalTownshipOf
    Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
  • D. hasHistoricTownRights
    Indicates that an entity possesses officially granted historic town rights, typically conferring a traditional legal or municipal status as a town.
  • E. hasHistoricCountyTownRelation
    Indicates a relationship where a town serves or has served as the historic county town (traditional administrative center) of a given county.
  • 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_69f34946a5208190bbd79f0fec4323bd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fffc783b648190bcd7df017514d206 completed May 10, 2026, 3:33 a.m.
PD Predicate disambiguation batch_69fffc03fa24819099e12413dc6e0afd completed May 10, 2026, 3:31 a.m.
Created at: May 1, 2026, 1:19 a.m.