Triple
T28942198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uptown |
E730479
|
entity |
| Predicate | hasNotablePercussionist |
P15280
|
FINISHED |
| Object | Cyril Neville |
—
|
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: Cyril Neville | Statement: [Uptown, hasNotablePercussionist, Cyril Neville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePercussionist Context triple: [Uptown, hasNotablePercussionist, Cyril Neville]
-
A.
hasPowerfulPercussion
Indicates that an entity features or produces percussion that is notably strong, intense, or forceful in impact.
-
B.
hasDrummer
chosen
Indicates that one entity serves as the drummer for, or plays drums in, another entity such as a band or musical group.
-
C.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
D.
notableKeyboardist
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
E.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: April 28, 2026, 8:37 a.m.