Triple
T32097421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sacred creative flame of Eru Ilúvatar |
E819753
|
entity |
| Predicate | loreSource |
P35890
|
FINISHED |
| Object | Tolkien’s letters |
—
|
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: Tolkien’s letters | Statement: [sacred creative flame of Eru Ilúvatar, loreSource, Tolkien’s letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreSource Context triple: [sacred creative flame of Eru Ilúvatar, loreSource, Tolkien’s letters]
-
A.
loreType
Indicates the category or kind of lore that characterizes or classifies a given entity or subject.
-
B.
scriptureOrLegendSource
chosen
Indicates that something is derived from, based on, or documented in a particular scripture or legendary source.
-
C.
knowledgeSourceInCanon
Indicates that the specified source of information is part of the officially recognized canon within a given universe or body of work.
-
D.
loreFunction
Indicates that something serves a narrative or world-building role within a fictional or informational context.
-
E.
knowledgeSourceInUniverse
Indicates that a particular source or repository of knowledge exists or is valid within a specified universe or contextual domain.
- 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_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. |
Created at: May 1, 2026, 12:26 a.m.