Triple
T350802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protestant Christianity |
E7436
|
entity |
| Predicate | hasViewOnLaity |
P11112
|
FINISHED |
| Object | all believers share spiritual priesthood |
—
|
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: all believers share spiritual priesthood | Statement: [Protestant Christianity, hasViewOnLaity, all believers share spiritual priesthood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnLaity Context triple: [Protestant Christianity, hasViewOnLaity, all believers share spiritual priesthood]
-
A.
hasLayMinistry
Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
hasViewOnSociety
Indicates that an entity holds a particular perspective, opinion, or stance regarding society or social structures.
-
D.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
E.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1f028c819098fa6480b4ca5cf0 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.