Triple
T3366896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Diocese of Montana |
E70857
|
entity |
| Predicate | usesClericalVestments |
P38265
|
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: [Episcopal Diocese of Montana, usesClericalVestments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClericalVestments Context triple: [Episcopal Diocese of Montana, usesClericalVestments, yes]
-
A.
hasClericalVestments
Indicates that one entity possesses or is associated with the clerical vestments (religious garments) of another entity.
-
B.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
C.
requiresVestments
chosen
Indicates that performing the related action or role necessitates wearing specific ceremonial or official vestments.
-
D.
aimsForLiturgicalUse
Indicates that something is intended or designed specifically for use in liturgical or formal religious worship contexts.
-
E.
hasLiturgicalPosture
Indicates that an entity is associated with a specific bodily posture or position used in a liturgical or religious ritual context.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb287a30c8190b4c40091675c94fb |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.