Triple
T8335706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Legacy |
E195780
|
entity |
| Predicate | releaseDateNintendoSwitch |
P44893
|
FINISHED |
| Object | 2023-11-14 |
—
|
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: 2023-11-14 | Statement: [Hogwarts Legacy, releaseDateNintendoSwitch, 2023-11-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDateNintendoSwitch Context triple: [Hogwarts Legacy, releaseDateNintendoSwitch, 2023-11-14]
-
A.
releaseDateOnPlatform
chosen
Indicates the date on which a particular item (e.g., a product, game, or media) becomes available on a specific platform.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
xboxSeriesReleaseDate
Indicates the calendar date on which a specific Xbox Series console or title was officially released.
-
D.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
E.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd3fc80819097b326119107ad4d |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.