Triple
T36611586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himring |
E903478
|
entity |
| Predicate | withstood |
P55657
|
FINISHED |
| Object | The 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: The Dagor Bragollach | Statement: [Himring, withstood, The Dagor Bragollach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withstood Context triple: [Himring, withstood, The Dagor Bragollach]
-
A.
endures
Indicates that an entity continues to exist, persist, or remain in a particular state or condition over a period of time, often despite challenges or changes.
-
B.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
C.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
resistedIn
chosen
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
E.
overcameHoldingOf
Indicates that one entity successfully defeated, reversed, or nullified another entity’s control, possession, or dominance over something.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.