Triple
T35364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judaism |
E699
|
entity |
| Predicate | hasViewOnScripture |
P2324
|
FINISHED |
| Object | Torah is divinely revealed |
—
|
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: Torah is divinely revealed | Statement: [Judaism, hasViewOnScripture, Torah is divinely revealed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnScripture Context triple: [Judaism, hasViewOnScripture, Torah is divinely revealed]
-
A.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
B.
sharesScriptureWith
Indicates that one entity communicates or distributes religious or scriptural texts to another entity.
-
C.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
D.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
E.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
- F. None of above. chosen
Provenance (4 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24989c3308190af59dfae37cfc32f |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a24873e97c8190b9e4279e43b6de14 |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a24988d4688190b4584356ed7dea50 |
completed | Feb. 28, 2026, 1:48 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.