Triple
T30680091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ήφαιστος |
E781027
|
entity |
| Predicate | αντιπαλότητα |
P129484
|
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.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
B.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
C.
petition
Indicates that one entity formally requests or appeals to another entity, typically an authority, for a specific action or change.
-
D.
antagonisticInteractionWith
chosen
Indicates a hostile or oppositional interaction in which one entity acts against, harms, or obstructs another.
-
E.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
- 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.