Triple
T30680092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ήφαιστος |
E781027
|
entity |
| Predicate | γλώσσα_μυθολογίας |
P22041
|
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.
languageOfMyths
chosen
Indicates that the subject is the language in which the myths associated with the object are told or recorded.
-
B.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
C.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
mythologicalTextMention
Indicates that a mythological text mentions, references, or otherwise explicitly refers to a given entity or concept.
- 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.