Triple
T20194462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volt Tackle |
E493045
|
entity |
| Predicate | requiresItemForBreeding |
P139144
|
FINISHED |
| Object | Light Ball |
—
|
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: Light Ball | Statement: [Volt Tackle, requiresItemForBreeding, Light Ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresItemForBreeding Context triple: [Volt Tackle, requiresItemForBreeding, Light Ball]
-
A.
breedingProduces
Indicates that a breeding process results in the creation or generation of one or more offspring or new entities.
-
B.
reproductionDependsOn
Indicates that the ability of one entity to reproduce is contingent upon the presence, condition, or actions of another entity.
-
C.
breedingType
Indicates the method or strategy by which organisms reproduce or are bred.
-
D.
fertilizationRequires
Indicates that a fertilization event can only occur if a specified condition, resource, or process is present or has taken place.
-
E.
breedingNote
Indicates notes or remarks documenting details, conditions, or observations related to a breeding event or process between entities.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7ed548190a893110fa2ffb144 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:37 p.m.