Triple
T6471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Church |
E129
|
entity |
| Predicate | liturgicalTradition |
P1104
|
FINISHED |
| Object | Anglican liturgy |
—
|
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: Anglican liturgy | Statement: [Episcopal Church, liturgicalTradition, Anglican liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalTradition Context triple: [Episcopal Church, liturgicalTradition, Anglican liturgy]
-
A.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
B.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
C.
denominationsInclude
Indicates that a set of denominations contains or encompasses a particular denomination as one of its members.
-
D.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
-
E.
formerReligiousAffiliation
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a242174cd4819095f78b221e1b41f1 |
completed | Feb. 28, 2026, 1:17 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.