Triple
T25760774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Priest |
E648733
|
entity |
| Predicate | churchOrientation |
P25565
|
FINISHED |
| Object | traditional Catholic |
—
|
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: traditional Catholic | Statement: [Sovereign Priest, churchOrientation, traditional Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchOrientation Context triple: [Sovereign Priest, churchOrientation, traditional Catholic]
-
A.
ecclesiasticalOrientation
Indicates the religious or church-related affiliation, tendency, or alignment of an entity within an ecclesiastical context.
-
B.
denominationalOrientation
chosen
Indicates the specific religious denomination or sect with which an entity is formally affiliated or aligned.
-
C.
liturgicalOrientation
Indicates the directional or positional alignment used in a religious or liturgical context, such as the way worship or ritual is oriented in space.
-
D.
withinChurch
Indicates that one entity is located inside or contained within a church.
-
E.
officialChurchOf
Indicates that one religious organization is formally recognized as the official church of a particular state, region, or governing body.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdeef1348190a32e4ae429680b7d |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:05 a.m.