Triple
T4632022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methodist Episcopal Church |
E101438
|
entity |
| Predicate | hasClericalOffice |
P19057
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [Methodist Episcopal Church, hasClericalOffice, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalOffice Context triple: [Methodist Episcopal Church, hasClericalOffice, bishop]
-
A.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
-
D.
hasClericalProvince
Indicates that one ecclesiastical jurisdiction or entity is part of, or belongs to, a specific clerical (church) province.
-
E.
hasAssociatedOffice
chosen
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a342ffc8190a911d0598ed230bb |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.