Triple
T19987913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Sword and Shield |
E493979
|
entity |
| Predicate | expansionPassReleaseDate |
P50108
|
FINISHED |
| Object | 2020-06-17 |
—
|
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: 2020-06-17 | Statement: [Pokémon Sword and Shield, expansionPassReleaseDate, 2020-06-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPassReleaseDate Context triple: [Pokémon Sword and Shield, expansionPassReleaseDate, 2020-06-17]
-
A.
expansionReleaseDate
chosen
Indicates the date on which an expansion (such as an add-on or supplementary release) is officially made available.
-
B.
expansionReleaseYear
Indicates the year in which an expansion (such as an add-on, DLC, or extended version) is officially released.
-
C.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
-
D.
alphaReleaseDate
Indicates the date on which an entity was first released in its alpha (early testing) version.
-
E.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:30 p.m.