Triple
T20600693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Crystal |
E506169
|
entity |
| Predicate | originalPlatformReleaseDateJapan |
P44893
|
FINISHED |
| Object | December 14, 2000 |
—
|
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: December 14, 2000 | Statement: [Pokémon Crystal, originalPlatformReleaseDateJapan, December 14, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlatformReleaseDateJapan Context triple: [Pokémon Crystal, originalPlatformReleaseDateJapan, December 14, 2000]
-
A.
releaseDateJapan
Indicates the date on which something is officially released or made available in Japan.
-
B.
releaseDateOnPlatform
chosen
Indicates the date on which a particular item (e.g., a product, game, or media) becomes available on a specific platform.
-
C.
releaseDateAsia
Indicates the date on which something is officially released or made available in Asian markets.
-
D.
releaseDateTaiwan
Indicates the date on which something (such as a product, film, or media) was officially released in Taiwan.
-
E.
marketedYearsInJapan
Indicates the years during which a product was actively marketed in Japan.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ffd088190adeacb9fe4907530 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.