Triple
T21649494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophets of Baal |
E534297
|
entity |
| Predicate | viewedAsByBiblicalAuthors |
P2324
|
FINISHED |
| Object | threat to covenant fidelity |
—
|
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: threat to covenant fidelity | Statement: [Prophets of Baal, viewedAsByBiblicalAuthors, threat to covenant fidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedAsByBiblicalAuthors Context triple: [Prophets of Baal, viewedAsByBiblicalAuthors, threat to covenant fidelity]
-
A.
viewedAsByBuddhistTexts
Indicates how something is regarded, interpreted, or characterized specifically within Buddhist texts.
-
B.
hasViewOnScripture
chosen
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
-
C.
isBiblicalVariantOf
Indicates that one textual form or reading is a variant version of another within the biblical textual tradition.
-
D.
consideredScriptureBy
Indicates that one party regards or recognizes a text or writing as sacred scripture.
-
E.
scriptureContributedTo
Indicates that an entity played a role in creating, authoring, or otherwise contributing content to a particular scripture or sacred 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59131c88819082df8e5b87f5954b |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.