Triple
T8815200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Shop Channel |
E209759
|
entity |
| Predicate | serviceLaunchDate |
P180
|
FINISHED |
| Object | 2006-11-19 |
—
|
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: 2006-11-19 | Statement: [Wii Shop Channel, serviceLaunchDate, 2006-11-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceLaunchDate Context triple: [Wii Shop Channel, serviceLaunchDate, 2006-11-19]
-
A.
serviceEntryDate
Indicates the date on which a service or duty officially began or was first entered into the record.
-
B.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
C.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
D.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.