Triple
T21278023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers: Combiner Wars |
E524441
|
entity |
| Predicate | toylineFeature |
P57584
|
FINISHED |
| Object | interchangeable limb robots |
—
|
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: interchangeable limb robots | Statement: [Transformers: Combiner Wars, toylineFeature, interchangeable limb robots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toylineFeature Context triple: [Transformers: Combiner Wars, toylineFeature, interchangeable limb robots]
-
A.
toyLine
Indicates that one entity is part of, or associated with, a particular toy product line or series.
-
B.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
C.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
D.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
E.
throughFeature
Indicates that one entity is connected to, accessed, or achieved by means of a particular feature or characteristic of 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73658f598819098a1192abfa40a12 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.