Triple
T22022665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock 'Em Sock 'Em Robots |
E543880
|
entity |
| Predicate | requiresPower |
P65082
|
FINISHED |
| Object | no batteries |
—
|
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: no batteries | Statement: [Rock 'Em Sock 'Em Robots, requiresPower, no batteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPower Context triple: [Rock 'Em Sock 'Em Robots, requiresPower, no batteries]
-
A.
requiresBattery
chosen
Indicates that one entity depends on a battery from another entity in order to function or be used.
-
B.
supportedPower
Indicates that an entity is capable of providing, handling, or operating at a specified level or range of power.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
E.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c8ac6881909a9e96e0873a3ae2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.