Triple
T20600697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Crystal |
E506169
|
entity |
| Predicate | virtualConsoleReleaseDateNorthAmerica |
P140724
|
FINISHED |
| Object | January 26, 2018 |
—
|
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: January 26, 2018 | Statement: [Pokémon Crystal, virtualConsoleReleaseDateNorthAmerica, January 26, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualConsoleReleaseDateNorthAmerica Context triple: [Pokémon Crystal, virtualConsoleReleaseDateNorthAmerica, January 26, 2018]
-
A.
virtualConsoleReleaseYear
Indicates the year in which something was released on a virtual console platform.
-
B.
virtualConsoleService
Indicates a relationship where a service provides or manages access to a virtual console interface for another entity.
-
C.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
consoleReleasePlatform
Indicates the specific gaming console or platform on which a particular release of a game or software is made available.
-
E.
virtualRealityVersionName
Indicates the name assigned to a specific version of a virtual reality experience, application, or environment.
- 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_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. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.