Triple

T28455932
Position Surface form Disambiguated ID Type / Status
Subject Port of Menteith parish E716712 entity
Predicate historicCountyJurisdiction P11889 FINISHED
Object Perthshire 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: Perthshire | Statement: [Port of Menteith parish, historicCountyJurisdiction, Perthshire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicCountyJurisdiction
Context triple: [Port of Menteith parish, historicCountyJurisdiction, Perthshire]
  • A. historicCountyPart
    Indicates that one entity forms a constituent part or subdivision of a historic county.
  • B. historicalJurisdiction chosen
    Indicates that one entity previously held legal or administrative authority over another entity during a past time period.
  • C. historicalCounty
    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.
  • D. countyJurisdiction
    Indicates that one entity (typically a government body or authority) has legal or administrative jurisdiction over a specific county.
  • E. historicCountyOverlap
    Indicates that two areas share a common portion of territory within the boundaries of the same historic county.
  • 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_69efd6b76f8c8190a7ba908aca280942 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69fe066d62b48190867df334039be786 completed May 8, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69fe03afde3c8190a5b9b0778d19eb1a completed May 8, 2026, 3:39 p.m.
Created at: April 28, 2026, 1:54 a.m.