Triple
T22571951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockaway Beach (live performances) |
E558094
|
entity |
| Predicate | typicalDrummer |
P148784
|
FINISHED |
| Object | Marky Ramone |
—
|
NE NERFINISHED |
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: Marky Ramone | Statement: [Rockaway Beach (live performances), typicalDrummer, Marky Ramone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDrummer Context triple: [Rockaway Beach (live performances), typicalDrummer, Marky Ramone]
-
A.
drummerOn
Indicates that one entity serves as the drummer or percussion performer for another entity, such as a band, ensemble, or musical project.
-
B.
usesDrums
Indicates that an entity employs drums as instruments or tools in performing an action or carrying out an activity.
-
C.
hasDrummer
Indicates that one entity serves as the drummer for, or plays drums in, another entity such as a band or musical group.
-
D.
hasDrummerWithNickname
Indicates that an entity has a drummer who is known or referred to by a specific nickname.
-
E.
accompanyingDrumType
Indicates the type of drum that is used to accompany or support another musical element, performance, or instrument.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fe958e881909b58a5439f2c6a35 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:52 p.m.