Triple
T20045352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pichu |
E497543
|
entity |
| Predicate | NationalPokédexNumber |
P138489
|
FINISHED |
| Object | 172 |
—
|
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: 172 | Statement: [Pichu, NationalPokédexNumber, 172]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NationalPokédexNumber Context triple: [Pichu, NationalPokédexNumber, 172]
-
A.
numberOfOriginalPokémon
Indicates the total count of original Pokémon associated with a given entity or context.
-
B.
isStarterPokémonIn
Indicates that a Pokémon serves as a starter Pokémon within a specified game, region, or context.
-
C.
legendaryPokémon
Indicates that the Pokémon is classified as a Legendary, typically denoting rarity, special lore significance, and exceptional power within the Pokémon universe.
-
D.
mainLegendaryPokémon
Indicates that one Pokémon serves as the primary or central legendary Pokémon associated with a particular context, such as a game, region, or storyline.
-
E.
introducedNewPokémonCount
Indicates the number of new Pokémon that were introduced in a given context or release.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eea09481908d1001165e9d719c |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:37 p.m.