Triple
T11146959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temurah |
E263692
|
entity |
| Predicate | discussesBiblicalSource |
P3661
|
FINISHED |
| Object | Leviticus 27:10 |
—
|
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: Leviticus 27:10 | Statement: [Temurah, discussesBiblicalSource, Leviticus 27:10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussesBiblicalSource Context triple: [Temurah, discussesBiblicalSource, Leviticus 27:10]
-
A.
scripturalExpertise
Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
-
B.
scripturalBasis
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
-
C.
scripturalBasisDebated
Indicates that whether this action or relationship is supported or justified by authoritative religious scriptures is a matter of dispute or disagreement.
-
D.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
E.
scripturalReference
chosen
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.