Triple
T30680086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ήφαιστος |
E781027
|
entity |
| Predicate | λατρευτικό_επίκεντρο |
P36126
|
FINISHED |
| Object | Ήφαιστείο Αθηνών |
—
|
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: Ήφαιστείο Αθηνών | Statement: [Ήφαιστος, λατρευτικό_επίκεντρο, Ήφαιστείο Αθηνών]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: λατρευτικό_επίκεντρο Context triple: [Ήφαιστος, λατρευτικό_επίκεντρο, Ήφαιστείο Αθηνών]
-
A.
centralEventOfPiety
Indicates that an event serves as the primary or focal act of religious devotion or pious practice within a given context.
-
B.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
-
C.
centerOfCult
chosen
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
D.
liturgicalCenter
Indicates that a place functions as the primary site for conducting and organizing liturgical or religious worship activities for a community.
-
E.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b1b21308190a63dc200654683fc |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.