Triple
T4867649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cohen |
E109009
|
entity |
| Predicate | religiousStatusAssociation |
P51786
|
FINISHED |
| Object | hereditary priestly lineage in Judaism |
—
|
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 priestly lineage in Judaism | Statement: [Cohen, religiousStatusAssociation, hereditary priestly lineage in Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousStatusAssociation Context triple: [Cohen, religiousStatusAssociation, hereditary priestly lineage in Judaism]
-
A.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
B.
churchStateRelation
Indicates the nature or degree of interaction, separation, or influence between religious institutions and governmental authority.
-
C.
civicStatus
Indicates the legal or social standing of an individual within a civic or societal framework, such as marital or citizenship status.
-
D.
associatedReligionRole
chosen
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
E.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7bb0b88190bbc24498619910fc |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.