Triple
T22022680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock 'Em Sock 'Em Robots |
E543880
|
entity |
| Predicate | gameBalance |
P118563
|
FINISHED |
| Object | symmetrical 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: symmetrical robots | Statement: [Rock 'Em Sock 'Em Robots, gameBalance, symmetrical robots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameBalance Context triple: [Rock 'Em Sock 'Em Robots, gameBalance, symmetrical robots]
-
A.
trainingBalance
Indicates the remaining amount or status of training resources, sessions, or credits available in a given training relationship or program.
-
B.
gameplayBasis
Indicates that one entity serves as the core mechanic, structure, or inspiration upon which another entity’s gameplay is designed or derived.
-
C.
gameplayImpact
chosen
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
D.
forceBalance
Indicates that the net forces acting on an entity or system are in equilibrium, resulting in no overall acceleration.
-
E.
powerBalance
Indicates the relative distribution of power or influence between entities in a relationship or interaction.
- 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.