Triple
T33217255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angerthas Moria |
E850319
|
entity |
| Predicate | hasGlyphs |
P84314
|
FINISHED |
| Object | runes for consonants |
—
|
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: runes for consonants | Statement: [Angerthas Moria, hasGlyphs, runes for consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlyphs Context triple: [Angerthas Moria, hasGlyphs, runes for consonants]
-
A.
hasGlyphsFor
chosen
Indicates that one entity provides or contains the necessary glyphs or visual symbols to represent another entity.
-
B.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
C.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
D.
hasTypography
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
E.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.