Triple
T27554100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Disaster of the Gladden Fields |
E695587
|
entity |
| Predicate | describesDeathOf |
P51826
|
FINISHED |
| Object | Isildur |
—
|
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: Isildur | Statement: [The Disaster of the Gladden Fields, describesDeathOf, Isildur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesDeathOf Context triple: [The Disaster of the Gladden Fields, describesDeathOf, Isildur]
-
A.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
B.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
-
C.
deathDescribedAs
Indicates that one entity characterizes, portrays, or refers to another entity’s death using a particular description, metaphor, or wording.
-
D.
containsDeathOf
chosen
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
E.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 1:36 p.m.