Triple
T36547524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bëor |
E901174
|
entity |
| Predicate | statusAfterDagorBragollach |
P200763
|
FINISHED |
| Object | largely destroyed |
—
|
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: largely destroyed | Statement: [House of Bëor, statusAfterDagorBragollach, largely destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterDagorBragollach Context triple: [House of Bëor, statusAfterDagorBragollach, largely destroyed]
-
A.
statusAfterBoromir
Indicates the state or condition of an entity that holds after the event or situation involving Boromir has occurred.
-
B.
outcomeForWitchKing
Indicates the resulting fate, consequence, or end state that befalls the Witch King.
-
C.
statusAfterBattleForLordaeron
Indicates the resulting state or condition of entities following the Battle for Lordaeron.
-
D.
outcomeForGandalf
Indicates the result or consequence that specifically befalls Gandalf in a given situation or event.
-
E.
timeOfExpulsionOfSauronFromDolGuldur
Indicates the point in time at which Sauron was driven out or expelled from Dol Guldur.
- 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_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69ffab59fe408190b72f13016de9953c |
completed | May 9, 2026, 9:47 p.m. |
Created at: May 3, 2026, 4:11 p.m.