Triple

T37766473
Position Surface form Disambiguated ID Type / Status
Subject Sinclairs of Orkney E941426 entity
Predicate historicallyHolds P203633 FINISHED
Object lands in Orkney — 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: lands in Orkney | Statement: [Sinclairs of Orkney, historicallyHolds, lands in Orkney]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyHolds
Context triple: [Sinclairs of Orkney, historicallyHolds, lands in Orkney]
  • A. hasHistoricBasisIn
    Indicates that something is grounded in, derived from, or justified by historical events, practices, or precedents.
  • B. hasHistoricity
    Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
  • C. historicallyGuardedBy
    Indicates that an entity was protected or defended by another entity during a past historical period.
  • D. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • E. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • 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_69f76ee3251881909bb4451aad50752b completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a01b935e3948190a7af37b07938d618 completed May 11, 2026, 11:10 a.m.
PD Predicate disambiguation batch_6a01b8d198b48190b01e16ac9ce7e7bd completed May 11, 2026, 11:09 a.m.
PDg Predicate description generation batch_6a01b9353e4c8190991c80e7c01a015b completed May 11, 2026, 11:10 a.m.
Created at: May 3, 2026, 4:19 p.m.