Triple
T2735888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of West Tennessee |
E60628
|
entity |
| Predicate | hasMissionStatementAspect |
P41737
|
FINISHED |
| Object | worship |
—
|
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: worship | Statement: [Diocese of West Tennessee, hasMissionStatementAspect, worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissionStatementAspect Context triple: [Diocese of West Tennessee, hasMissionStatementAspect, worship]
-
A.
hasMissionStatement
Indicates that an entity possesses a formal mission statement that articulates its core purpose, goals, or guiding principles.
-
B.
hasEducationalMission
Indicates that an entity is responsible for or engaged in carrying out an educational purpose, goal, or function.
-
C.
hasMissionAgency
Indicates that an entity is associated with, overseen by, or carried out under the responsibility of a particular mission agency.
-
D.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
E.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd968b2148190929af432c9d8001f |
completed | March 7, 2026, 7:53 a.m. |
Created at: March 6, 2026, 9:56 p.m.