Triple
T35920761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo e-Reader |
E1038876
|
entity |
| Predicate | discontinuationYearJapan |
P188479
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Nintendo e-Reader, discontinuationYearJapan, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discontinuationYearJapan Context triple: [Nintendo e-Reader, discontinuationYearJapan, 2004]
-
A.
discontinuationAnnouncementYear
Indicates the year in which the discontinuation of something (such as a product, service, or program) was officially announced.
-
B.
brandDiscontinuationYear
Indicates the year in which a brand ceased operations or was officially discontinued.
-
C.
hasDiscontinuationApproxYear
Indicates that an entity ceased to exist, operate, or be available around a specified (approximate) calendar year.
-
D.
discontinuationApproximateDate
Indicates the approximate date on which something is discontinued or ceases to be available or in effect.
-
E.
decommissionedByJapan
Indicates that Japan officially took a given object, facility, or system out of active service or use.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:07 p.m.