Triple
T34344385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Fairbanks |
E881388
|
entity |
| Predicate | hasNativeMinistry |
P48213
|
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, hasNativeMinistry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNativeMinistry Context triple: [Diocese of Fairbanks, hasNativeMinistry, yes]
-
A.
hasLayMinistry
Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
-
B.
hasMinistries
Indicates that an entity possesses, oversees, or is organized into one or more ministries as subordinate units or departments.
-
C.
hasEthnicMinistry
chosen
Indicates that an entity maintains or is associated with a ministry or organizational unit dedicated to serving a specific ethnic group or groups.
-
D.
hasNoDedicatedMinistry
Indicates that an entity (such as a policy area or function) is not overseen by its own separate, specialized ministry.
-
E.
hasMediaMinistry
Indicates that an entity operates, oversees, or is associated with a ministry or department responsible for media-related affairs.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 1, 2026, 1:58 a.m.