Triple
T534114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province VIII |
E12288
|
entity |
| Predicate | ChristianTradition |
P11528
|
FINISHED |
| Object | Episcopal |
—
|
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: Episcopal | Statement: [Province VIII, ChristianTradition, Episcopal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChristianTradition Context triple: [Province VIII, ChristianTradition, Episcopal]
-
A.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
B.
worshipTradition
chosen
Indicates that one entity follows, practices, or is associated with a particular religious or spiritual worship tradition.
-
C.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
-
D.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
E.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.