Triple
T30680008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Επιμηθέας |
E781026
|
entity |
| Predicate | έπαιξεΡόλοΣε |
P1668
|
FINISHED |
| Object | άνοιγμα του πιθαριού της Πανδώρας |
—
|
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: άνοιγμα του πιθαριού της Πανδώρας | Statement: [Επιμηθέας, έπαιξεΡόλοΣε, άνοιγμα του πιθαριού της Πανδώρας]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: έπαιξεΡόλοΣε Context triple: [Επιμηθέας, έπαιξεΡόλοΣε, άνοιγμα του πιθαριού της Πανδώρας]
-
A.
playedRoleIn
chosen
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
playedEarlyRoleIn
Indicates that one entity contributed significantly to the initial or formative stages of another entity’s development, success, or emergence.
-
C.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
D.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
როლები
Indicates that an entity has specific roles, functions, or positions assigned or associated with it in a given context.
- 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.