Triple
T29247206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atomiswave |
E741470
|
entity |
| Predicate | inputStandard |
P132538
|
FINISHED |
| Object | arcade joysticks and buttons |
—
|
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: arcade joysticks and buttons | Statement: [Atomiswave, inputStandard, arcade joysticks and buttons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputStandard Context triple: [Atomiswave, inputStandard, arcade joysticks and buttons]
-
A.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
B.
isStandardIn
Indicates that something conforms to or is officially recognized as the accepted standard within a particular context or system.
-
C.
inputIs
chosen
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
D.
standardOutput
Indicates that one entity produces data or results that are directed to another entity’s standard output stream.
-
E.
becameStandardIn
Indicates that something was adopted and recognized as the standard within a particular context, domain, or time period.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6648a17708190a2b19c610549b5e5 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:33 p.m.