Triple
T33812173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegon I Targaryen |
E866564
|
entity |
| Predicate | swornEnemy |
P172646
|
FINISHED |
| Object | Harren Hoare |
—
|
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: Harren Hoare | Statement: [Aegon I Targaryen, swornEnemy, Harren Hoare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swornEnemy Context triple: [Aegon I Targaryen, swornEnemy, Harren Hoare]
-
A.
wasEnemyOf
chosen
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
B.
formerEnemyOf
Indicates that one entity was previously an enemy of another entity, but that adversarial relationship no longer holds.
-
C.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
D.
initiallyEnemyOf
Indicates that one entity starts out in a state of enmity or opposition toward another at the beginning of a specified time or situation.
-
E.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffcee3a88190951fe0720bfc8fa4 |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.