Triple
T3461718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Alaska |
E73039
|
entity |
| Predicate | usesEpiscopalPolity |
P6330
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Diocese of Alaska, usesEpiscopalPolity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEpiscopalPolity Context triple: [Diocese of Alaska, usesEpiscopalPolity, yes]
-
A.
usesEpiscopalSuccession
Indicates that one entity maintains its authority or leadership through a line of bishops consecrated in an unbroken chain from earlier bishops (episcopal succession).
-
B.
ecclesiasticalPolity
chosen
Indicates the form, structure, and governing system by which a religious or church organization is administered and its authority is distributed.
-
C.
usesEpiscopalChurchCanons
Indicates that one party applies or follows the official canons (laws and regulations) of the Episcopal Church in their actions or decisions.
-
D.
isOnlyEpiscopalDioceseIn
Indicates that an episcopal diocese is the sole diocese of its kind within a specified geographic or organizational area.
-
E.
hasEpiscopalAreaScheme
Indicates that an entity is associated with, or governed according to, a particular episcopal area organizational scheme.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae745e081909007cd3a664c57f3 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.