Triple
T34344384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Fairbanks |
E881388
|
entity |
| Predicate | hasMissionParishes |
P192003
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Diocese of Fairbanks, hasMissionParishes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissionParishes Context triple: [Diocese of Fairbanks, hasMissionParishes, yes]
-
A.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
-
B.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
C.
hasParishJurisdiction
Indicates that one entity holds official parish-level authority or administrative control over another entity or area.
-
D.
hasParallelDiocese
Indicates that one diocese corresponds to and operates in parallel with another diocese, typically covering the same or overlapping territory or community under a different jurisdiction or tradition.
-
E.
hasDiocesesOrDistricts
Indicates that an organization or authority oversees one or more dioceses or districts within its jurisdiction.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 1, 2026, 1:58 a.m.