Triple
T35013678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenshade |
E1009996
|
entity |
| Predicate | gameReleaseContext |
P182008
|
FINISHED |
| Object | The Elder Scrolls Online base game |
—
|
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: The Elder Scrolls Online base game | Statement: [Greenshade, gameReleaseContext, The Elder Scrolls Online base game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameReleaseContext Context triple: [Greenshade, gameReleaseContext, The Elder Scrolls Online base game]
-
A.
videoGameReleaseYear
Indicates the calendar year in which a particular video game was released.
-
B.
sourceGameReleasePeriod
Indicates the time period during which the source game was originally released.
-
C.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
studioRelease
Indicates that a work (such as a film, album, or game) is officially released or distributed by a particular studio.
-
E.
releaseDateOnPlatform
Indicates the date on which a particular item (e.g., a product, game, or media) becomes available on a specific platform.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.