Triple
T30211444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Poseidon Hippios |
E768076
|
entity |
| Predicate | veneratedAspectOfDeity |
P73550
|
FINISHED |
| Object | Poseidon Hippios |
—
|
NE NERFINISHED |
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: Poseidon Hippios | Statement: [cult of Poseidon Hippios, veneratedAspectOfDeity, Poseidon Hippios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedAspectOfDeity Context triple: [cult of Poseidon Hippios, veneratedAspectOfDeity, Poseidon Hippios]
-
A.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
-
B.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
C.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
D.
hasDeityAspect
chosen
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
E.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:32 p.m.