Triple
T1774688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Amiga 1000 |
E38950
|
entity |
| Predicate | keyboardType |
P16221
|
FINISHED |
| Object | detachable keyboard |
—
|
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: detachable keyboard | Statement: [Commodore Amiga 1000, keyboardType, detachable keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyboardType Context triple: [Commodore Amiga 1000, keyboardType, detachable keyboard]
-
A.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
hasKeyboard
chosen
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
D.
kitType
Indicates the specific category or configuration of a kit associated with an entity or activity.
-
E.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.