Triple
T30800298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of the Lonely Mountain |
E784345
|
entity |
| Predicate | valueTo |
P21465
|
FINISHED |
| Object | Dwarves of Erebor |
—
|
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: Dwarves of Erebor | Statement: [Heart of the Lonely Mountain, valueTo, Dwarves of Erebor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueTo Context triple: [Heart of the Lonely Mountain, valueTo, Dwarves of Erebor]
-
A.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
B.
takesValueOn
Indicates that one entity assumes, is assigned, or exhibits a particular value in relation to another entity or context.
-
C.
valuedBy
chosen
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
E.
value1CorrespondsTo
Indicates that one value is directly associated with, matches, or maps to another value in a defined correspondence.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:42 p.m.