Triple
T30633135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seven Rings for the Dwarf-lords |
E779762
|
entity |
| Predicate | lineFromRhyme |
P54123
|
FINISHED |
| Object | Seven for the Dwarf-lords in their halls of stone |
—
|
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: Seven for the Dwarf-lords in their halls of stone | Statement: [The Seven Rings for the Dwarf-lords, lineFromRhyme, Seven for the Dwarf-lords in their halls of stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineFromRhyme Context triple: [The Seven Rings for the Dwarf-lords, lineFromRhyme, Seven for the Dwarf-lords in their halls of stone]
-
A.
hasRhymeLine
chosen
Indicates that one line of text rhymes with another line.
-
B.
hasRhymingText
Indicates that two pieces of text share a rhyming relationship, typically ending with similar or identical sounds.
-
C.
rhymeSchemeParodied
Indicates that one work imitates or mocks the rhyme scheme pattern of another work.
-
D.
rhymeScheme
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
E.
refrainWord
Indicates that one entity avoids using, mentioning, or expressing a particular word or term in relation to another entity or context.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1ee6348190a316b92bccd14826 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.