Triple
T31863430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corky Laing |
E813391
|
entity |
| Predicate | notableSongAsDrummer |
P207535
|
FINISHED |
| Object | Mississippi Queen |
E1542256
|
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: Mississippi Queen | Statement: [Corky Laing, notableSongAsDrummer, Mississippi Queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSongAsDrummer Context triple: [Corky Laing, notableSongAsDrummer, Mississippi Queen]
-
A.
notableSongContributions
Indicates that an entity has made significant creative or performance contributions to one or more songs.
-
B.
notableSongsIncluded
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
-
C.
hasFamousVersionDrummer
Indicates that an entity has a well-known or widely recognized version whose role is specifically that of a drummer.
-
D.
notableKeyboardist
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
E.
hasDrummer
Indicates that one entity serves as the drummer for, or plays drums in, another entity such as a band or musical group.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fd7854c81908ae406f984d9940f |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
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 30, 2026, 11:53 p.m.