Triple
T19077754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 12 |
E466947
|
entity |
| Predicate | containsDivineSpeech |
P112600
|
FINISHED |
| Object | God’s call to Abram |
—
|
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: God’s call to Abram | Statement: [Genesis 12, containsDivineSpeech, God’s call to Abram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDivineSpeech Context triple: [Genesis 12, containsDivineSpeech, God’s call to Abram]
-
A.
containsDivineName
Indicates that the referenced entity includes or explicitly mentions a divine or sacred name within its content.
-
B.
containsDivineNamesSection
Indicates that something includes a dedicated section specifically for listing or discussing divine names.
-
C.
divineInstruction
Indicates that one entity issues a command, guidance, or directive to another that is understood to originate from a divine or sacred source.
-
D.
recordsDivineStatement
chosen
Indicates that one entity documents or preserves a statement, message, or pronouncement made by a divine being.
-
E.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.