Triple
T26690303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Algeria |
E672859
|
entity |
| Predicate | nunciatureLocatedIn |
P17859
|
FINISHED |
| Object | Algiers |
—
|
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: Algiers | Statement: [Catholic Church in Algeria, nunciatureLocatedIn, Algiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nunciatureLocatedIn Context triple: [Catholic Church in Algeria, nunciatureLocatedIn, Algiers]
-
A.
isArchdioceseSeatOf
Indicates that a particular archdiocese serves as the central ecclesiastical jurisdiction and administrative seat for a specified church region or authority.
-
B.
cityOfTitularChurch
Indicates the city in which a given titular church is located.
-
C.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
-
D.
supremePontiffResidence
Indicates the residence associated with the supreme pontiff (e.g., where the supreme pontiff officially lives or is based).
-
E.
seatOfPlenipotentiaryRepresentative
chosen
Indicates the location or institution that serves as the official base or office for a plenipotentiary representative.
- 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_69f61741857c81909cbe2fa1583dcaec |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:25 a.m.