Triple
T9248726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makey Makey Classic |
E222262
|
entity |
| Predicate | languageFreeInteraction |
P7055
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Makey Makey Classic, languageFreeInteraction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFreeInteraction Context triple: [Makey Makey Classic, languageFreeInteraction, yes]
-
A.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
B.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
C.
lessMutuallyIntelligibleThan
Indicates that the level of mutual intelligibility between one pair of languages (or language varieties) is lower than that between another pair.
-
D.
dialogueWith
Indicates that two entities are engaged in a mutual conversational exchange or dialogue with each other.
-
E.
languageNeutral
chosen
Indicates that the relationship or action is independent of any specific natural language, applying uniformly across different linguistic contexts.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f6d62c8190a1e33f1854767b47 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.