Triple
T26690300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Algeria |
E672859
|
entity |
| Predicate | hasBishopConference |
P25417
|
FINISHED |
| Object | Algerian Episcopal Conference |
—
|
NE NERFINISHED |
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: Algerian Episcopal Conference | Statement: [Catholic Church in Algeria, hasBishopConference, Algerian Episcopal Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBishopConference Context triple: [Catholic Church in Algeria, hasBishopConference, Algerian Episcopal Conference]
-
A.
hasBishopsConference
chosen
Indicates that an entity is associated with or belongs to a particular bishops' conference.
-
B.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
-
C.
hasHouseOfBishops
Indicates that an organization or body includes or is associated with a specific House of Bishops as part of its structure or governance.
-
D.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
E.
includesBishops
Indicates that one entity contains or has among its members one or more bishops.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 3:25 a.m.