Triple
T32113219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meriadoc Brandybuck |
E820170
|
entity |
| Predicate | helpedDefeat |
P22407
|
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: [Meriadoc Brandybuck, helpedDefeat, Witch-king of Angmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedDefeat Context triple: [Meriadoc Brandybuck, helpedDefeat, Witch-king of Angmar]
-
A.
sideDefeated
Indicates that one side in a conflict, competition, or contest has been beaten or overcome by another side.
-
B.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
C.
defeatedDespite
Indicates that one entity successfully defeated another entity even though circumstances or expectations suggested that defeat would be unlikely or difficult.
-
D.
overthrownWithHelpOf
chosen
Indicates that one entity was removed from power or defeated through the assistance, support, or intervention of another specified entity.
-
E.
defeatedToRestore
Indicates that one entity was overcome or subdued in order to bring another entity, state, or condition back to its previous or proper form.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b90568648190ac60ea9e5c686dfe |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:27 a.m.