Triple
T37142530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fingolfin’s realm in Hithlum |
E920152
|
entity |
| Predicate | destroyedOrOverrunIn |
P31453
|
FINISHED |
| Object | Dagor Bragollach |
—
|
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: Dagor Bragollach | Statement: [Fingolfin’s realm in Hithlum, destroyedOrOverrunIn, Dagor Bragollach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedOrOverrunIn Context triple: [Fingolfin’s realm in Hithlum, destroyedOrOverrunIn, Dagor Bragollach]
-
A.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.