Triple
T2684489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Lexington |
E57450
|
entity |
| Predicate | mainDenominationalFamily |
P25565
|
FINISHED |
| Object | Anglican |
—
|
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: Anglican | Statement: [Diocese of Lexington, mainDenominationalFamily, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDenominationalFamily Context triple: [Diocese of Lexington, mainDenominationalFamily, Anglican]
-
A.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
B.
hasDenominationalCounterpart
Indicates that one entity has a corresponding or equivalent entity in another religious denomination or branch.
-
C.
denominationalOrientation
chosen
Indicates the specific religious denomination or sect with which an entity is formally affiliated or aligned.
-
D.
religionDominantBranch
Indicates that one religious branch is the primary or most prevalent form of a broader religion within a given context or population.
-
E.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9edba5c8190b86d6cba0f1964e2 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.