Triple
T31214114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get on the Floor |
E795824
|
entity |
| Predicate | notableBassPlayer |
P207374
|
FINISHED |
| Object | Louis Johnson |
E1029203
|
NE 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: Louis Johnson | Statement: [Get on the Floor, notableBassPlayer, Louis Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBassPlayer Context triple: [Get on the Floor, notableBassPlayer, Louis Johnson]
-
A.
notableKeyboardist
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
B.
bassistOnMostRecordings
Indicates that the referenced person serves as the bass player on the majority of a specified artist’s or group’s recordings.
-
C.
hasNotableBassline
Indicates that something (typically a piece of music) features a bassline that is particularly prominent, distinctive, or otherwise noteworthy.
-
D.
notableLuthier
Indicates that a person is recognized as a distinguished or prominent maker of stringed musical instruments (a luthier).
-
E.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
- F. None of above. chosen
Provenance (5 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b1438c5308190a2f21c6aa4e52b20 |
completed | June 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:09 p.m.