Triple
T24981006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Aeolus |
E625166
|
entity |
| Predicate | hasNotableTragicFigure |
P97477
|
FINISHED |
| Object | Athamas |
—
|
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: Athamas | Statement: [House of Aeolus, hasNotableTragicFigure, Athamas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTragicFigure Context triple: [House of Aeolus, hasNotableTragicFigure, Athamas]
-
A.
hasNotableMilitaryFigure
Indicates that an entity is associated with or distinguished by a specific person recognized for significant military role, rank, or achievements.
-
B.
hasNotablePeople
chosen
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
C.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
hasTragicEnding
Indicates that the event, story, or situation concludes with a sorrowful, disastrous, or otherwise deeply unfortunate outcome.
-
E.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 6:02 a.m.