Triple
T5926463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acheloos River |
E131821
|
entity |
| Predicate | wasWorshippedAs |
P8132
|
FINISHED |
| Object | sacred river in antiquity |
—
|
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: sacred river in antiquity | Statement: [Acheloos River, wasWorshippedAs, sacred river in antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasWorshippedAs Context triple: [Acheloos River, wasWorshippedAs, sacred river in antiquity]
-
A.
worshippedAs
chosen
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
B.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
C.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
D.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
-
E.
worshippedDuring
Indicates that a religious figure, deity, or sacred object is the target of worship specifically during a given time period, event, or occasion.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.