Triple
T1926223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JoyLabz |
E40836
|
entity |
| Predicate | MakeyMakeyFeature |
P6774
|
FINISHED |
| Object | maps touch to keyboard and mouse inputs |
—
|
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: maps touch to keyboard and mouse inputs | Statement: [JoyLabz, MakeyMakeyFeature, maps touch to keyboard and mouse inputs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MakeyMakeyFeature Context triple: [JoyLabz, MakeyMakeyFeature, maps touch to keyboard and mouse inputs]
-
A.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
B.
technologicalFeature
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
C.
scriptInventor
Indicates that one entity is the creator or originator of a particular writing system or script used by another entity.
-
D.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb261ef8481909be2390ac5a02622 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.