Triple
T21649560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confrontation with Elijah on Mount Carmel |
E534299
|
entity |
| Predicate | hasNumberOfProphetsOfAsherah |
P144858
|
FINISHED |
| Object | 400 |
—
|
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: 400 | Statement: [Confrontation with Elijah on Mount Carmel, hasNumberOfProphetsOfAsherah, 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfProphetsOfAsherah Context triple: [Confrontation with Elijah on Mount Carmel, hasNumberOfProphetsOfAsherah, 400]
-
A.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
-
B.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
D.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
E.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
- 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_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. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:35 p.m.