Triple

T7063746
Position Surface form Disambiguated ID Type / Status
Subject Balfron E164289 entity
Predicate locatedInHistoricalCounty P1069 FINISHED
Object Stirlingshire 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: Stirlingshire | Statement: [Balfron, locatedInHistoricalCounty, Stirlingshire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInHistoricalCounty
Context triple: [Balfron, locatedInHistoricalCounty, Stirlingshire]
  • A. historicalCounty chosen
    Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
  • B. locatedInHistoricSite
    Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
  • C. hasHistoricCountySeat
    Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
  • D. hasHistoricCountyStatusSince
    Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
  • E. hasHistoricCountyNumber
    Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
  • 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_69c688796c148190adb2f1596f595f22 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4a3c36c819080942c59f1830ae8 completed March 27, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69c6e1bdc1f08190975fcdbbb1854d1e completed March 27, 2026, 7:59 p.m.
Created at: March 27, 2026, 2:38 p.m.