Triple

T34419743
Position Surface form Disambiguated ID Type / Status
Subject Petty, Inverness-shire E883492 entity
Predicate historicalParishChurch P101108 FINISHED
Object Petty Parish Church 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: Petty Parish Church | Statement: [Petty, Inverness-shire, historicalParishChurch, Petty Parish Church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalParishChurch
Context triple: [Petty, Inverness-shire, historicalParishChurch, Petty Parish Church]
  • A. isHistoricChurchIn
    Indicates that a church, recognized as historic, is located within a specified geographic area or jurisdiction.
  • B. isParishChurch
    Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
  • C. hasParishChurchArchitecturalInterest
    Indicates that a parish church possesses notable architectural features or significance.
  • D. governingDioceseHistorical
    Indicates that one diocese historically exercised governing authority or jurisdiction over another ecclesiastical entity.
  • E. isHistoricParishOf chosen
    Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
  • 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_69f349c2e3b88190a67834eb5bcffeaf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a0064f8efa48190956287f548a8057d completed May 10, 2026, 10:59 a.m.
PD Predicate disambiguation batch_6a006471e75c8190adae99bd75e7411b completed May 10, 2026, 10:56 a.m.
Created at: May 1, 2026, 2 a.m.