Triple
T6746779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaritans |
E154236
|
entity |
| Predicate | traditionalPriesthood |
P72718
|
FINISHED |
| Object | hereditary high priest |
—
|
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: hereditary high priest | Statement: [Samaritans, traditionalPriesthood, hereditary high priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPriesthood Context triple: [Samaritans, traditionalPriesthood, hereditary high priest]
-
A.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
-
B.
priests
Indicates that the subject serves in a religious or spiritual officiating role, typically performing sacred rituals or duties for a faith community.
-
C.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
D.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b8a0f0819086b802983e8ffcb6 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.