Triple
T34291332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Yakima |
E879895
|
entity |
| Predicate | hasRuralMinistry |
P40297
|
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 Yakima, hasRuralMinistry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuralMinistry Context triple: [Diocese of Yakima, hasRuralMinistry, yes]
-
A.
hasRuralDevelopmentDepartment
Indicates that an entity possesses or includes a department responsible for rural development activities or functions.
-
B.
hasRuralCouncilStatus
Indicates that an entity holds the official designation or legal status of a rural council within a given administrative or governance system.
-
C.
hasMinistries
chosen
Indicates that an entity possesses, oversees, or is organized into one or more ministries as subordinate units or departments.
-
D.
hasRuralFocus
Indicates that the subject is oriented toward, concerned with, or primarily serving rural areas or rural-related issues.
-
E.
hasRuralBaseParty
Indicates that a political party’s primary support, organization, or operational base is located in rural areas rather than urban centers.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:57 a.m.