Triple

T28446942
Position Surface form Disambiguated ID Type / Status
Subject Anglican Church in colonial South Carolina E715864 entity
Predicate hasNotableParish P199250 FINISHED
Object St. Philip’s Parish, Charleston 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: St. Philip’s Parish, Charleston | Statement: [Anglican Church in colonial South Carolina, hasNotableParish, St. Philip’s Parish, Charleston]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableParish
Context triple: [Anglican Church in colonial South Carolina, hasNotableParish, St. Philip’s Parish, Charleston]
  • A. hasMainParish
    Indicates that an entity is associated with or administered by a specific primary parish.
  • B. hasParishChurchesIn
    Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
  • C. hasNotableTown
    Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
  • D. hasRuralParish
    Indicates that an entity possesses or is associated with a rural parish as an administrative or ecclesiastical subdivision.
  • E. hasParishHouse
    Indicates that a church or parish entity possesses or is associated with a specific parish house building.
  • 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_69ff289541e0819096eeceb8e6332650 completed May 9, 2026, 12:29 p.m.
PD Predicate disambiguation batch_69ff281ab1988190920f0443be9f10cc completed May 9, 2026, 12:27 p.m.
PDg Predicate description generation batch_69ff28948b34819090e7e8b0b19535b2 completed May 9, 2026, 12:29 p.m.
Created at: April 28, 2026, 1:49 a.m.