Triple
T314953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makey Makey extension |
E7685
|
entity |
| Predicate | requiresHardware |
P100
|
FINISHED |
| Object | Makey Makey invention kit |
—
|
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: Makey Makey invention kit | Statement: [Makey Makey extension, requiresHardware, Makey Makey invention kit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresHardware Context triple: [Makey Makey extension, requiresHardware, Makey Makey invention kit]
-
A.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
C.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea62f830819089e94b3aa3e4e187 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.