Triple
T19520100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers: Animated |
E488379
|
entity |
| Predicate | featuresTransformation |
P68295
|
FINISHED |
| Object | robots to vehicles |
—
|
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 to vehicles | Statement: [Transformers: Animated, featuresTransformation, robots to vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTransformation Context triple: [Transformers: Animated, featuresTransformation, robots to vehicles]
-
A.
featuresTransformationOf
chosen
Indicates that something includes or presents a transformation or change applied to another entity.
-
B.
featuresInversion
Indicates that one entity exhibits or incorporates an inversion of another entity, such as a reversed, mirrored, or otherwise inverted form or structure.
-
C.
featureDesigner
Indicates that a person serves as the designer responsible for creating or specifying a particular feature.
-
D.
featuresCreator
Indicates that an entity prominently presents, highlights, or showcases a particular creator as a key associated party.
-
E.
featuresMethod
Indicates that an entity includes or provides a particular method as part of its functionality or behavior.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359feb808190ba94563831adc720 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7d0da88190aabf8b5799691fb1 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.