Triple
T33112244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Araphor |
E847359
|
entity |
| Predicate | enemyRuler |
P108097
|
FINISHED |
| Object | Witch-king of Angmar |
—
|
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: Witch-king of Angmar | Statement: [Araphor, enemyRuler, Witch-king of Angmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyRuler Context triple: [Araphor, enemyRuler, Witch-king of Angmar]
-
A.
opponentMonarch
Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
-
B.
enemyCharacter
chosen
Indicates that one character is hostile or opposed to another, typically treating them as an adversary or foe.
-
C.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
D.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
E.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ec34a481908851cd68697cb88c |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.