Triple

T2317764
Position Surface form Disambiguated ID Type / Status
Subject Northumberland E51104 entity
Predicate historicalBorderRole P29914 FINISHED
Object Anglo-Scottish border county 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 county | Statement: [Northumberland, historicalBorderRole, Anglo-Scottish border county]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalBorderRole
Context triple: [Northumberland, historicalBorderRole, Anglo-Scottish border county]
  • A. borderHistory
    Indicates the historical changes, events, or status of borders between entities over time.
  • B. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
  • C. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • D. historicalRegionCorrespondsTo
    Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
  • E. hasHistoricTerritory
    Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
  • 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_69a88b074b908190ae983dbca7757d88 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc685f05481909c863b29d1f6bacd completed March 7, 2026, 6:32 a.m.
PD Predicate disambiguation batch_69abc5909cc48190aab257313542dc49 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:49 p.m.