Triple
T20193401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charizard |
E493024
|
entity |
| Predicate | evolutionStage |
P41864
|
FINISHED |
| Object | final |
—
|
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: final | Statement: [Charizard, evolutionStage, final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionStage Context triple: [Charizard, evolutionStage, final]
-
A.
evolutionaryPhase
chosen
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
B.
evolutionaryPosition
Indicates the relative placement of an entity within an evolutionary sequence or lineage, such as its stage, branching point, or order of emergence in evolutionary history.
-
C.
evolvedOver
Indicates that one entity has changed or developed into another entity across a span of time.
-
D.
evolvesIn
Indicates that an entity undergoes a process of change or development within a specified environment, context, or medium.
-
E.
evolutionControlledBy
Indicates that the process or course of evolution of an entity is directed, regulated, or determined by another entity.
- 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.