Triple
T19987923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Sword and Shield |
E493979
|
entity |
| Predicate | battleFormatIntroduced |
P138227
|
FINISHED |
| Object | Max Raid Battle |
—
|
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: Max Raid Battle | Statement: [Pokémon Sword and Shield, battleFormatIntroduced, Max Raid Battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleFormatIntroduced Context triple: [Pokémon Sword and Shield, battleFormatIntroduced, Max Raid Battle]
-
A.
yearOfFirstBattle
Indicates the specific year in which the first battle involving the given entities took place.
-
B.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
C.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
D.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
E.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
- 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_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. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:30 p.m.