Triple
T36547809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of Beleriand |
E901180
|
entity |
| Predicate | destroyedRegion |
P186041
|
FINISHED |
| Object | Doriath |
—
|
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: Doriath | Statement: [sinking of Beleriand, destroyedRegion, Doriath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedRegion Context triple: [sinking of Beleriand, destroyedRegion, Doriath]
-
A.
remnantRegion
Indicates that a region is a leftover or remaining part of something that previously existed or was larger.
-
B.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
C.
regionDrained
Indicates that one region serves as the drainage area for another, collecting and channeling its surface or groundwater flow.
-
D.
destroyedPart
Indicates that one entity has caused damage to or ruined a portion or component of another entity.
-
E.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
- F. None of above. chosen
Provenance (4 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.