Triple
T34424444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makkot |
E883630
|
entity |
| Predicate | basedOnBiblicalSource |
P2326
|
FINISHED |
| Object | Book of Deuteronomy |
—
|
NE NERFINISHED |
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: Book of Deuteronomy | Statement: [Makkot, basedOnBiblicalSource, Book of Deuteronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnBiblicalSource Context triple: [Makkot, basedOnBiblicalSource, Book of Deuteronomy]
-
A.
scripturalBasis
chosen
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
-
B.
scripturalSourceType
Indicates the type or category of source from which a scriptural text or reference is derived.
-
C.
scripturalEvidence
Indicates that one entity serves as supporting scriptural or textual proof for the truth, validity, or relevance of another entity.
-
D.
hasTheologicalSourceIn
Indicates that something derives its theological basis, authority, or origin from a specified source.
-
E.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 2 a.m.