Triple

T28446935
Position Surface form Disambiguated ID Type / Status
Subject Anglican Church in colonial South Carolina E715864 entity
Predicate parishModel P165159 FINISHED
Object English parish system 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 parish system | Statement: [Anglican Church in colonial South Carolina, parishModel, English parish system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parishModel
Context triple: [Anglican Church in colonial South Carolina, parishModel, English parish system]
  • A. parish
    Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
  • B. parishIncludes
    Indicates that a parish geographically or administratively contains or encompasses another entity or area.
  • C. parishWith
    Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
  • D. parishName
    Indicates that an entity has the specified parish as its official or recorded name.
  • E. isChristianParish
    Indicates that one entity is a Christian parish, i.e., an administrative or ecclesiastical unit within a Christian church associated with a particular community or territory.
  • 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_69efd6b44550819094ae991b553d9fc3 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f65705a3048190a3728b695ba2ae65 completed May 2, 2026, 7:56 p.m.
PD Predicate disambiguation batch_69f651a931748190a637e631a52bbfaa completed May 2, 2026, 7:34 p.m.
PDg Predicate description generation batch_69f6562ef4e4819082ce6abd41b74dc5 completed May 2, 2026, 7:53 p.m.
Created at: April 28, 2026, 1:49 a.m.