Triple
T10538397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Diocese of Navajoland |
E248630
|
entity |
| Predicate | hasMinistryArea |
P64534
|
FINISHED |
| Object | evangelism |
—
|
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: evangelism | Statement: [Episcopal Diocese of Navajoland, hasMinistryArea, evangelism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinistryArea Context triple: [Episcopal Diocese of Navajoland, hasMinistryArea, evangelism]
-
A.
ministryArea
Indicates that one entity is the geographic or administrative area over which a ministry or ministerial body has responsibility or jurisdiction.
-
B.
hasMinistries
Indicates that an entity possesses, oversees, or is organized into one or more ministries as subordinate units or departments.
-
C.
belongsToMinistry
Indicates that one entity is under the authority, administration, or organizational control of a specific ministry.
-
D.
hasMinistryContext
chosen
Indicates that something is associated with, occurs within, or is defined in the context of a particular ministry or ministerial setting.
-
E.
hasManagementArea
Indicates that one entity is responsible for managing, overseeing, or administering a specified area or region.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a56133c819088285522e64831f7 |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.