Triple
T20193840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johto |
E493032
|
entity |
| Predicate | hasEvilTeamActivity |
P19746
|
FINISHED |
| Object | Team Rocket revival in Generation II games |
—
|
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: Team Rocket revival in Generation II games | Statement: [Johto, hasEvilTeamActivity, Team Rocket revival in Generation II games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvilTeamActivity Context triple: [Johto, hasEvilTeamActivity, Team Rocket revival in Generation II games]
-
A.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
B.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
D.
hasInsurgentGroupActivity
Indicates that insurgent groups are actively operating or conducting activities in relation to the referenced entity or context.
-
E.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7270081908ed8513a8363e9b1 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.