Triple
T33217302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angerthas Erebor |
E850320
|
entity |
| Predicate | hasGraphemeType |
P180674
|
FINISHED |
| Object | runes |
—
|
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 | Statement: [Angerthas Erebor, hasGraphemeType, runes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGraphemeType Context triple: [Angerthas Erebor, hasGraphemeType, runes]
-
A.
hasGraphemeShapeOrigin
Indicates that one grapheme’s shape is derived or originates from the shape of another grapheme or graphical form.
-
B.
hasGraphemeToPhonemeRelation
Indicates a relationship where a written symbol or sequence of symbols (grapheme) is systematically associated with a corresponding sound or sequence of sounds (phoneme).
-
C.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
D.
hasRadicalType
Indicates that an entity is associated with or classified by a specific type of radical (e.g., chemical, linguistic, or structural radical).
-
E.
codePointType
Indicates the classification or category assigned to a specific Unicode code point (such as letter, digit, punctuation, etc.).
- F. None of above. chosen
Provenance (4 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:30 a.m.