Triple
T20193699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Unite |
E493030
|
entity |
| Predicate | releaseDateMobile |
P180
|
FINISHED |
| Object | 2021-09-22 |
—
|
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: 2021-09-22 | Statement: [Pokémon Unite, releaseDateMobile, 2021-09-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseDateMobile Context triple: [Pokémon Unite, releaseDateMobile, 2021-09-22]
-
A.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
B.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
D.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
E.
releasedUnder
Indicates that one entity is made available, distributed, or published according to the terms, conditions, or authority specified by another entity (such as a license, label, or governing framework).
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7270081908ed8513a8363e9b1 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.