Triple
T9692947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Bishops |
E234577
|
entity |
| Predicate | denominationalOfficeType |
P89654
|
FINISHED |
| Object | board of bishops |
—
|
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: board of bishops | Statement: [Board of Bishops, denominationalOfficeType, board of bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationalOfficeType Context triple: [Board of Bishops, denominationalOfficeType, board of bishops]
-
A.
denominationalHost
Indicates that one entity serves as the hosting or organizing body for a religious denomination-related event, activity, or function involving another entity.
-
B.
denominationalStatus
Indicates the religious denomination or sect to which an entity is formally affiliated or classified.
-
C.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
D.
denominationalControl
Indicates that an organization, institution, or entity is governed, overseen, or significantly influenced by a specific religious denomination.
-
E.
denominationalOrientation
Indicates the specific religious denomination or sect with which an entity is formally affiliated or aligned.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0727908190897894151c0ee7c2 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.