Triple

T28853407
Position Surface form Disambiguated ID Type / Status
Subject historic county of Bute E728665 entity
Predicate hasHistoricSheriffdom P192487 FINISHED
Object Sheriffdom of Bute (historical) 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: Sheriffdom of Bute (historical) | Statement: [historic county of Bute, hasHistoricSheriffdom, Sheriffdom of Bute (historical)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricSheriffdom
Context triple: [historic county of Bute, hasHistoricSheriffdom, Sheriffdom of Bute (historical)]
  • A. hasHistoricSheriffdomStatus
    Indicates that an entity holds or held the official status of a historic sheriffdom within a given jurisdiction.
  • B. hasHistoricCountySeat
    Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
  • C. hasHistoricCountyStatusSince
    Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
  • D. hasAssociatedHistoricCounty
    Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
  • E. hasHistoricHamlets
    Indicates that an entity possesses or is associated with one or more historically recognized hamlets.
  • F. None of above. chosen

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_69f0319f4e5481909e4c439dbe8be940 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69fd0d0ba5c48190bddb3f0e6637544c completed May 7, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69fd0c4324a8819086c90adf46216e0e completed May 7, 2026, 10:03 p.m.
PDg Predicate description generation batch_69fd0d0aebac8190868a7714ddb4f1fd completed May 7, 2026, 10:07 p.m.
Created at: April 28, 2026, 6:44 a.m.