Triple
T29220116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pull Me Under |
E740783
|
entity |
| Predicate | hasKeyboardStyle |
P177141
|
FINISHED |
| Object | atmospheric keyboards |
—
|
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: atmospheric keyboards | Statement: [Pull Me Under, hasKeyboardStyle, atmospheric keyboards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyboardStyle Context triple: [Pull Me Under, hasKeyboardStyle, atmospheric keyboards]
-
A.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
B.
hasKeyboardRange
Indicates that one entity possesses or supports a specified span of keys or notes across a keyboard-based input or instrument.
-
C.
hasKeyboardCount
Indicates the number of keyboards associated with a given entity.
-
D.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
E.
hasKeypadLayout
Indicates that one entity possesses or uses a specific arrangement or configuration of keys or buttons provided by another entity.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 12:15 p.m.