Triple

T80633
Position Surface form Disambiguated ID Type / Status
Subject Shrewsbury, Shropshire, England E1618 entity
Predicate hasHistoricMarketCharter P1614 FINISHED
Object medieval period 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 period | Statement: [Shrewsbury, Shropshire, England, hasHistoricMarketCharter, medieval period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricMarketCharter
Context triple: [Shrewsbury, Shropshire, England, hasHistoricMarketCharter, medieval period]
  • A. hasHistoricIndustry
    Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
  • B. hasHistoricalContext
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • C. hasTradingDays
    Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
  • D. hasHistoricalOrigin chosen
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • E. hasMarket
    Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
  • 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_69a24c60d19c8190a1b6c105ca59ef5b completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a25053ca208190a371b0d38000c2b9 completed Feb. 28, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69a24eb2998c819082681da74601d446 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.