Triple
T32097041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durin's Bane |
E819745
|
entity |
| Predicate | awakensBy |
P173557
|
FINISHED |
| Object | Dwarven mining in Moria |
—
|
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: Dwarven mining in Moria | Statement: [Durin's Bane, awakensBy, Dwarven mining in Moria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakensBy Context triple: [Durin's Bane, awakensBy, Dwarven mining in Moria]
-
A.
awakensIn
Indicates that one entity comes out of sleep or becomes conscious while located within or inside another entity.
-
B.
awakensInYear
Indicates that an entity becomes awake or active starting in a specified calendar year.
-
C.
ageOfAwakening
Indicates the specific age at which an entity becomes aware, conscious, or begins its significant period of activity or development.
-
D.
risesOn
Indicates that one entity ascends, increases, or moves upward in position, level, or value relative to another reference point or context.
-
E.
wakeWord
Indicates that one entity serves as the activation phrase or trigger word used to wake up or activate another entity (such as a device or system).
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b643d5008190b789f0a4d3288fa3 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.