Triple
T13595270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | clavinet |
E324800
|
entity |
| Predicate | keyboardRange |
P28992
|
FINISHED |
| Object | 60 keys |
—
|
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: 60 keys | Statement: [clavinet, keyboardRange, 60 keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyboardRange Context triple: [clavinet, keyboardRange, 60 keys]
-
A.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
B.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
C.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
D.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
designedRange
Indicates the intended or specified range within which something is designed to operate or be effective.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.