Triple
T9477230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Toss |
E228545
|
entity |
| Predicate | actionCommand |
P78655
|
FINISHED |
| Object | hold and release the A button |
—
|
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: hold and release the A button | Statement: [Shell Toss, actionCommand, hold and release the A button]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionCommand Context triple: [Shell Toss, actionCommand, hold and release the A button]
-
A.
formerCommand
Indicates that one entity previously held command or leadership authority over another entity but no longer does.
-
B.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
-
C.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
D.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
E.
ConcreteCommand
chosen
Indicates a specific, fully defined instruction or operation that can be executed directly without further interpretation or refinement.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.