Triple
T13074209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elder Scrolls Online: Summerset |
E329529
|
entity |
| Predicate | addsStoryFeature |
P82895
|
FINISHED |
| Object | time-bending Psijic abilities |
—
|
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: time-bending Psijic abilities | Statement: [The Elder Scrolls Online: Summerset, addsStoryFeature, time-bending Psijic abilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsStoryFeature Context triple: [The Elder Scrolls Online: Summerset, addsStoryFeature, time-bending Psijic abilities]
-
A.
featureAdded
chosen
Indicates that a new feature has been introduced or incorporated into a system, product, or entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d981160e388190bab942a2ded2903e |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.