Triple
T3670227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asherah |
E77859
|
entity |
| Predicate | worshipSite |
P14925
|
FINISHED |
| Object | high places |
—
|
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: high places | Statement: [Asherah, worshipSite, high places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipSite Context triple: [Asherah, worshipSite, high places]
-
A.
worshipCenter
chosen
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
B.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
-
C.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
D.
countryOfWorshipSite
Indicates that a place of worship is located within the borders of a specified country.
-
E.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42c96648190abbd5d23b25d6a6b |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.