Triple
T22803734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishlegs Ingerman |
E564471
|
entity |
| Predicate | dragonSpeciesPartner |
P74771
|
FINISHED |
| Object | Gronckle |
—
|
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: Gronckle | Statement: [Fishlegs Ingerman, dragonSpeciesPartner, Gronckle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dragonSpeciesPartner Context triple: [Fishlegs Ingerman, dragonSpeciesPartner, Gronckle]
-
A.
enemySpecies
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
-
B.
partnerPokémon
Indicates that one entity is the designated partner Pokémon of another entity, typically signifying a primary, ongoing companion relationship.
-
C.
appearsWithSpecies
Indicates that one entity is observed or recorded together with a particular species in the same context or occurrence.
-
D.
memberSpecies
Indicates that a particular species is a constituent or member of a larger biological or taxonomic group.
-
E.
associatedCharacterSpecies
chosen
Indicates that one entity is related to, or linked with, the species of a particular character.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5a7c2881909a7aaacddd09f00c |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.