Triple

T28671318
Position Surface form Disambiguated ID Type / Status
Subject 53rd (Shropshire) Regiment of Foot E725725 entity
Predicate servedInRegion P6665 FINISHED
Object North America 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: North America | Statement: [53rd (Shropshire) Regiment of Foot, servedInRegion, North America]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedInRegion
Context triple: [53rd (Shropshire) Regiment of Foot, servedInRegion, North America]
  • A. formerServesRegion
    Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
  • B. operatedInRegion chosen
    Indicates that an entity conducted operations or activities within a specified geographic region.
  • C. servedProvince
    Indicates that an entity has provided services or held jurisdictional authority over a specified province.
  • D. isInhabitedRegionServed
    Indicates that a particular inhabited region is provided with services or coverage by a specified entity (such as an organization, facility, or infrastructure).
  • E. servesRegionAcrossFrom
    Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
  • 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_69f01d85be388190b669a0e401e2f2c4 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69fd783fed9c81909e792702636c4f1f completed May 8, 2026, 5:44 a.m.
PD Predicate disambiguation batch_69fd7788e63c81909de22fdafcfe41c0 completed May 8, 2026, 5:41 a.m.
Created at: April 28, 2026, 5:03 a.m.