Triple
T30001649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Pro (16-inch, 2019) |
E762184
|
entity |
| Predicate | replacedKeyboardType |
P177141
|
FINISHED |
| Object | butterfly 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: butterfly keyboard | Statement: [MacBook Pro (16-inch, 2019), replacedKeyboardType, butterfly keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedKeyboardType Context triple: [MacBook Pro (16-inch, 2019), replacedKeyboardType, butterfly keyboard]
-
A.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
B.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
C.
hasKeyboardStyle
chosen
Indicates the type or style of keyboard associated with or used by an entity.
-
D.
replacedSurfaceType
Indicates that one surface type has been substituted or changed to another surface type.
-
E.
hasKeyboardBy
Indicates that an entity is equipped with or uses a keyboard provided, installed, or controlled by another entity.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 29, 2026, 6:41 p.m.