Triple
T16376513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branchidae |
E397691
|
entity |
| Predicate | typeOfPriesthood |
P113742
|
FINISHED |
| Object | clan-based 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: clan-based priesthood | Statement: [Branchidae, typeOfPriesthood, clan-based priesthood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPriesthood Context triple: [Branchidae, typeOfPriesthood, clan-based priesthood]
-
A.
hasViewOnPriesthood
Indicates that an entity holds a particular stance, opinion, or doctrinal position regarding the concept, role, or practice of priesthood.
-
B.
traditionalPriesthood
Indicates that an entity holds or is associated with a priestly role rooted in longstanding, customary, or historically established religious practices.
-
C.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
-
D.
priesthoodDescribedBy
chosen
Indicates that a priesthood is documented, characterized, or explained by a particular description or source.
-
E.
hasMarriedPriesthoodTradition
Indicates that a religious group or denomination maintains a tradition in which members of its priesthood are permitted or expected to be married.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d79df8819087285b9457b7bdb6 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.