Triple

T33217258
Position Surface form Disambiguated ID Type / Status
Subject Angerthas Moria E850319 entity
Predicate alsoKnownAs P39 FINISHED
Object Dwarven runes of Moria
Dwarven runes of Moria are a specialized variant of the Cirth runic script used by the Dwarves of Khazad-dûm in J.R.R. Tolkien’s Middle-earth legendarium.
E2041716 NE 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 runes of Moria | Statement: [Angerthas Moria, alsoKnownAs, Dwarven runes of Moria]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Dwarven runes of Moria
Triple: [Angerthas Moria, alsoKnownAs, Dwarven runes of Moria]
Generated description
Dwarven runes of Moria are a specialized variant of the Cirth runic script used by the Dwarves of Khazad-dûm in J.R.R. Tolkien’s Middle-earth legendarium.

Provenance (5 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_69f3496083dc8190b229bb6932dc548b completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6da678a0481909abb150e315b8710 completed May 3, 2026, 5:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a352fd03ccc819081cb55be2dd5f163 completed June 19, 2026, 12:02 p.m.
NEDg Description generation batch_6a3530bad8d481909632310de9202d68 completed June 19, 2026, 12:06 p.m.
NED2 Entity disambiguation (via description) batch_6a35325603588190bc3f2996b913be4e completed June 19, 2026, 12:13 p.m.
Created at: May 1, 2026, 1:30 a.m.