Triple
T20306926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bösendorfer piano |
E510130
|
entity |
| Predicate | hasKeyboardRange |
P139604
|
FINISHED |
| Object | 88 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: 88 keys | Statement: [Bösendorfer piano, hasKeyboardRange, 88 keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyboardRange Context triple: [Bösendorfer piano, hasKeyboardRange, 88 keys]
-
A.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
B.
hasKeyboardCount
Indicates the number of keyboards associated with a given entity.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
E.
isKeyboardWork
Indicates that an activity or task primarily involves using a keyboard as the main mode of work or input.
- F. None of above. chosen
Provenance (4 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6774068c08190824fa55438bab712 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:18 a.m.