Triple

T33392783
Position Surface form Disambiguated ID Type / Status
Subject Barony of Wrottesley E855091 entity
Predicate associatedHistoricCounty P152728 FINISHED
Object Staffordshire E25231 NE 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: Staffordshire | Statement: [Barony of Wrottesley, associatedHistoricCounty, Staffordshire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedHistoricCounty
Context triple: [Barony of Wrottesley, associatedHistoricCounty, Staffordshire]
  • A. hasAssociatedHistoricCounty chosen
    Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
  • B. historicalCounty
    Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
  • C. coversHistoricCounty
    Indicates that one entity geographically encompasses the area of a historic county.
  • D. historicCountyPart
    Indicates that one entity forms a constituent part or subdivision of a historic county.
  • 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 (4 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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a358148096c8190bdbd6dbd806a207c completed June 19, 2026, 5:50 p.m.
PD Predicate disambiguation batch_6a0379f505c88190ac0879ab422c3054 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:35 a.m.