Triple
T19987904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Sword and Shield |
E493979
|
entity |
| Predicate | numberOfRegionalFormsIntroduced |
P138225
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Pokémon Sword and Shield, numberOfRegionalFormsIntroduced, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRegionalFormsIntroduced Context triple: [Pokémon Sword and Shield, numberOfRegionalFormsIntroduced, 13]
-
A.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
B.
numberOfRegions
Indicates the total count of distinct regions associated with or contained within a given entity.
-
C.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
D.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
E.
numberOfNewRegions
Indicates the count of regions that have been newly created or added within a specified context or time frame.
- 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:29 p.m.