Triple
T36134716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Omaha |
E1045131
|
entity |
| Predicate | hasArchbishopResidence |
P177970
|
FINISHED |
| Object | Omaha |
—
|
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: Omaha | Statement: [Archdiocese of Omaha, hasArchbishopResidence, Omaha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchbishopResidence Context triple: [Archdiocese of Omaha, hasArchbishopResidence, Omaha]
-
A.
hasArchbishopric
Indicates that a given place, church, or ecclesiastical jurisdiction serves as the seat or domain of an archbishop.
-
B.
hasBishopResidence
Indicates that a bishop has an official residence at a specified location.
-
C.
metropolitanArchbishopResidesIn
chosen
Indicates that a metropolitan archbishop has their official residence or seat in a specified place or jurisdiction.
-
D.
hasArchdiocese
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
-
E.
isArchdioceseSeatOf
Indicates that a particular archdiocese serves as the central ecclesiastical jurisdiction and administrative seat for a specified church region or authority.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:08 p.m.