Triple
T29011248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Paintbrush |
E736569
|
entity |
| Predicate | inputDeviceSupport |
P2571
|
FINISHED |
| Object | two-button mouse |
—
|
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: two-button mouse | Statement: [PC Paintbrush, inputDeviceSupport, two-button mouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputDeviceSupport Context triple: [PC Paintbrush, inputDeviceSupport, two-button mouse]
-
A.
inputDevice
chosen
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
-
C.
supportsKeyboardAndMouse
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdc78c481908836151d03329ae7 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:42 a.m.