Triple
T35012897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rihad |
E1009977
|
entity |
| Predicate | appearsInLoreOf |
P178803
|
FINISHED |
| Object | The Elder Scrolls series |
—
|
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: The Elder Scrolls series | Statement: [Rihad, appearsInLoreOf, The Elder Scrolls series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInLoreOf Context triple: [Rihad, appearsInLoreOf, The Elder Scrolls series]
-
A.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
appearsInAppendicesOf
Indicates that one entity is included or referenced within the appendices section of another entity.
-
C.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
D.
inGameLoreSource
Indicates that the information or content originates from narrative or explanatory material within the game’s own lore or story universe.
-
E.
seriesLore
chosen
Indicates that one entity provides backstory, world-building, or canonical background information that enriches the overarching narrative of a series in which the other entity appears.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.