Triple
T11660597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo eShop |
E277107
|
entity |
| Predicate | launchDateOnPlatform |
P44893
|
FINISHED |
| Object | 2012-12-08 (Wii U) |
—
|
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: 2012-12-08 (Wii U) | Statement: [Nintendo eShop, launchDateOnPlatform, 2012-12-08 (Wii U)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDateOnPlatform Context triple: [Nintendo eShop, launchDateOnPlatform, 2012-12-08 (Wii U)]
-
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.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
launchPlatformName
Indicates the name of the platform or site from which a launch (typically of a vehicle, rocket, or mission) is conducted.
-
E.
hasOnlinePlatformRelease
Indicates that an entity has been released or made available through an online platform or digital service.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.