Triple

T26753356
Position Surface form Disambiguated ID Type / Status
Subject ceremonial county of Northumberland E674600 entity
Predicate historicBorderRole P47008 FINISHED
Object Anglo-Scottish border region 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: Anglo-Scottish border region | Statement: [ceremonial county of Northumberland, historicBorderRole, Anglo-Scottish border region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicBorderRole
Context triple: [ceremonial county of Northumberland, historicBorderRole, Anglo-Scottish border region]
  • A. historicBoundaryFor chosen
    Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
  • B. borderHistory
    Indicates the historical changes, events, or status of borders between entities over time.
  • C. historicalFrontier
    Indicates a boundary or border that historically separated two regions, territories, or spheres of influence.
  • D. borderRegionRole
    Indicates a role or function that an entity has specifically in relation to a border region or border area.
  • E. hasBorderTownRole
    Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
  • 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_69eecda6e9dc81908452fab3ba17ed9b completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: April 27, 2026, 3:54 a.m.