Triple

T19980486
Position Surface form Disambiguated ID Type / Status
Subject Barony of Forth E493803 entity
Predicate hasHistoricalRegionType P138147 FINISHED
Object English-speaking colony 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: English-speaking colony | Statement: [Barony of Forth, hasHistoricalRegionType, English-speaking colony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalRegionType
Context triple: [Barony of Forth, hasHistoricalRegionType, English-speaking colony]
  • A. isHistoricRegionFor
    Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
  • B. hasHistoricRegionStyle
    Indicates that an entity exhibits or is characterized by the architectural or cultural style associated with a particular historic region.
  • C. historicalRegionCorrespondsTo
    Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
  • D. isInHistoricRegion
    Indicates that an entity is located within or belongs to a historically recognized geographic region.
  • E. historicalRegionCode
    Indicates that an entity is associated with a specific code identifying a historical region.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65d12d968819081e315ec4585cd9f completed April 20, 2026, 5:06 p.m.
PD Predicate disambiguation batch_69e537fae79c81909eae39500766d0b6 completed April 19, 2026, 8:15 p.m.
PDg Predicate description generation batch_69e543c42c688190a22f4d31ec692377 completed April 19, 2026, 9:06 p.m.
Created at: April 11, 2026, 3:28 p.m.