Triple
T19361141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temurah textual tradition |
E484281
|
entity |
| Predicate | relatedHermeneutic |
P128816
|
FINISHED |
| Object | Gematria |
—
|
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: Gematria | Statement: [Temurah textual tradition, relatedHermeneutic, Gematria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedHermeneutic Context triple: [Temurah textual tradition, relatedHermeneutic, Gematria]
-
A.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
B.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
theologicalInterpretation
Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
-
D.
relevanceToBiblicalStudies
chosen
Indicates that something has significance, usefulness, or meaningful connection to the study, interpretation, or understanding of the Bible and related scholarship.
-
E.
intertextualRelation
Indicates a relationship in which one text references, echoes, or otherwise meaningfully connects to another text.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190c2a8081908f48dfa738248ec8 |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.