Triple
T36711402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadok |
E906802
|
entity |
| Predicate | biblicalFigureType |
P27433
|
FINISHED |
| Object | 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: priest | Statement: [Zadok, biblicalFigureType, priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalFigureType Context triple: [Zadok, biblicalFigureType, priest]
-
A.
biblicalFigure
Indicates that an entity is recognized as a person mentioned or characterized within the Bible.
-
B.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
-
D.
biblicalSourceCharacter
Indicates that one entity is the character or figure that serves as the source or origin for another entity within a biblical context.
-
E.
religiousFigureType
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c813c44481908d6a261afcf6f857 |
completed | May 3, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.