Triple

T9737326
Position Surface form Disambiguated ID Type / Status
Subject Maaseik E236095 entity
Predicate hasHistoricCenterType P49037 FINISHED
Object medieval street pattern LITERAL 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: medieval street pattern | Statement: [Maaseik, hasHistoricCenterType, medieval street pattern]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricCenterType
Context triple: [Maaseik, hasHistoricCenterType, medieval street pattern]
  • A. hasHistoricCenterStatus
    Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
  • B. hasHistoricCenterShape chosen
    Indicates the geometric form or configuration that characterizes the historic center of a place or settlement.
  • C. isInHistoricCenterOf
    Indicates that one entity is located within the historic center area of another entity (typically a city or town).
  • D. isHistoricCenterOf
    Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
  • E. historicallyImportantCenter
    Indicates that a place has served as a significant focal point of historical events, activities, or influence.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9ef032088190acd94c35b89e48b7 completed April 1, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69cd03c6ffc88190a5e9569e19122ad5 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:22 p.m.