Triple
T18779980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Isengard |
E459230
|
entity |
| Predicate | holderDownfallEvent |
P26452
|
FINISHED |
| Object | destruction of Isengard by the Ents |
—
|
LITERAL FINISHED |
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: destruction of Isengard by the Ents | Statement: [Lord of Isengard, holderDownfallEvent, destruction of Isengard by the Ents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderDownfallEvent Context triple: [Lord of Isengard, holderDownfallEvent, destruction of Isengard by the Ents]
-
A.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
downfall
Indicates the process or event by which an entity experiences a significant decline, ruin, or loss of power, status, or success.
-
C.
hadTyrant
Indicates that an entity was ruled or dominated by a tyrant.
-
D.
fellFromFavorUnder
Indicates that an entity lost approval, status, or support while another specified party was in power or in a position of authority.
-
E.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933e35a481908c21f7f488e1dd99 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.