Triple
T37142411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thargelion |
E920149
|
entity |
| Predicate | destroyedOrLostIn |
P31453
|
FINISHED |
| Object | end of Beleriand after the War of Wrath |
—
|
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: end of Beleriand after the War of Wrath | Statement: [Thargelion, destroyedOrLostIn, end of Beleriand after the War of Wrath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedOrLostIn Context triple: [Thargelion, destroyedOrLostIn, end of Beleriand after the War of Wrath]
-
A.
lostOrDestroyed
Indicates that something has ceased to exist in its original, usable form, either by being misplaced beyond recovery or physically destroyed.
-
B.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
C.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
D.
lostToSea
Indicates that something has been carried away or disappeared into the sea, resulting in its loss.
-
E.
shipLostWith
Indicates that one entity was lost together with another entity in the same maritime incident or disappearance.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.