Triple
T18589111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers: Beast Wars |
E454311
|
entity |
| Predicate | transformationTheme |
P132696
|
FINISHED |
| Object | robots transform into animals |
—
|
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: robots transform into animals | Statement: [Transformers: Beast Wars, transformationTheme, robots transform into animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformationTheme Context triple: [Transformers: Beast Wars, transformationTheme, robots transform into animals]
-
A.
themeChange
Indicates that an entity undergoes a change in its theme, style, or subject, typically transitioning from one thematic state or configuration to another.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
dataTheme
Indicates the primary subject area or thematic category that the associated data pertains to.
-
D.
undergoesTheme
Indicates that an entity experiences or is subjected to a process, event, or change described by another entity or action.
-
E.
themeInArc
Indicates that something serves as a central theme or recurring subject within a particular narrative arc.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b3e564819088e60fc25d1976f0 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.