Triple
T16276665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Council of the Russian Orthodox Church |
E395145
|
entity |
| Predicate | includesBishops |
P122481
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Local Council of the Russian Orthodox Church, includesBishops, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBishops Context triple: [Local Council of the Russian Orthodox Church, includesBishops, true]
-
A.
includedBishopsFrom
Indicates that a group, document, or event contains or incorporates bishops originating from a specified source or location.
-
B.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
-
C.
hasBishopsConference
Indicates that an entity is associated with or belongs to a particular bishops' conference.
-
D.
isCatholicBishop
Indicates that a person holds the office of bishop within the Roman Catholic Church.
-
E.
majorityOfBishopsFrom
Indicates that, within a given group or context, more than half of the bishops originate from or are associated with a specified place or source.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460ea5a4819099f779288a754c8d |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.