Triple
T36017835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezir |
E1041894
|
entity |
| Predicate | hasPriestlyDivision |
—
|
GENERATED |
| Object | Benei Hezir division |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriestlyDivision Context triple: [Hezir, hasPriestlyDivision, Benei Hezir division]
-
A.
priestlyDivision
chosen
Indicates a relationship where an individual is assigned to or associated with a specific priestly division or order within a religious hierarchy.
-
B.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
C.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
- F. None of above.
Provenance (1 batch)
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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.