Triple
T2827907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priesthood of Jesus |
E54967
|
entity |
| Predicate | interpretsOldTestament |
P5494
|
FINISHED |
| Object | Levitical 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: Levitical priesthood | Statement: [Priesthood of Jesus, interpretsOldTestament, Levitical priesthood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsOldTestament Context triple: [Priesthood of Jesus, interpretsOldTestament, Levitical priesthood]
-
A.
theologicalInterpretation
chosen
Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
-
B.
oldTestamentSourceText
Indicates that something originates from, is based on, or is drawn from a text in the Old Testament.
-
C.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
D.
styleOfExegesis
Indicates the particular interpretive method or approach applied when analyzing or explaining a text.
-
E.
OldTestamentFirstPublished
Indicates that the Old Testament was first made publicly available in written or printed form at a particular time or by a particular edition.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde95d8148190bcae8b0659a5c116 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.