Triple
T20193453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulbasaur |
E493025
|
entity |
| Predicate | evolutionFamily |
P138494
|
FINISHED |
| Object | Bulbasaur evolutionary line |
—
|
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: Bulbasaur evolutionary line | Statement: [Bulbasaur, evolutionFamily, Bulbasaur evolutionary line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionFamily Context triple: [Bulbasaur, evolutionFamily, Bulbasaur evolutionary line]
-
A.
evolutionLine
chosen
Indicates that one entity is part of, or connected within, a sequence of evolutionary stages leading from one form to another.
-
B.
evolvedWith
Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
-
C.
evolvedUnder
Indicates that one entity developed or changed over time while being influenced or shaped by specific conditions, factors, or an environment represented by the other entity.
-
D.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
E.
modernNameEvolvedVia
Indicates that a modern name developed or was derived from an earlier form through a process of change or evolution.
- 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.