Triple
T19851965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Micah |
E477016
|
entity |
| Predicate | hasTypeOfPriesthood |
P3092
|
FINISHED |
| Object | non-centralized 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: non-centralized priesthood | Statement: [House of Micah, hasTypeOfPriesthood, non-centralized priesthood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPriesthood Context triple: [House of Micah, hasTypeOfPriesthood, non-centralized priesthood]
-
A.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
-
B.
hasViewOnPriesthood
Indicates that an entity holds a particular stance, opinion, or doctrinal position regarding the concept, role, or practice of priesthood.
-
C.
associatedWithPriesthood
Indicates a relationship in which an entity has a connection, role, or involvement with a priesthood or priestly office.
-
D.
hasMarriedPriesthoodTradition
Indicates that a religious group or denomination maintains a tradition in which members of its priesthood are permitted or expected to be married.
-
E.
hasClergyType
chosen
Indicates the specific category or role of clergy associated with an entity.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65869e1b481908e2a2a2074ff4a6d |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.