Triple
T29024442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barad-dûr |
E737548
|
entity |
| Predicate | destroyedWhen |
P11808
|
FINISHED |
| Object | the One Ring was 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: the One Ring was destroyed | Statement: [Barad-dûr, destroyedWhen, the One Ring was destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedWhen Context triple: [Barad-dûr, destroyedWhen, the One Ring was destroyed]
-
A.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
C.
possiblyDestroyedIn
Indicates that an entity may have been destroyed during or as a result of a specified event or situation.
-
D.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
E.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66007a5d8819085fcc6651a89a189 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:51 a.m.