Triple
T25607899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aethiopis |
E641962
|
entity |
| Predicate | mainHeroicOpponents |
P81119
|
FINISHED |
| Object | Achilles and Memnon |
—
|
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: Achilles and Memnon | Statement: [Aethiopis, mainHeroicOpponents, Achilles and Memnon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainHeroicOpponents Context triple: [Aethiopis, mainHeroicOpponents, Achilles and Memnon]
-
A.
hasMythologicalOpponents
Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
-
B.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
C.
primaryAntagonists
chosen
Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
-
D.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
E.
enemyCharacter
Indicates that one character is hostile or opposed to another, typically treating them as an adversary or foe.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e0d2e88190b51e1eded1627f94 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:39 p.m.