Triple
T22893674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despina |
E568108
|
entity |
| Predicate | worshipCharacter |
P150156
|
FINISHED |
| Object | local and esoteric |
—
|
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: local and esoteric | Statement: [Despina, worshipCharacter, local and esoteric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipCharacter Context triple: [Despina, worshipCharacter, local and esoteric]
-
A.
worshippedByCharacter
Indicates that a character is the object of religious or devoted worship performed by another character.
-
B.
worshipSymbol
Indicates a relationship where one entity venerates, honors, or directs religious devotion toward another entity as a sacred symbol.
-
C.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
D.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
E.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f17fc76be48190af9aa54a84b2d7bf |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:40 p.m.