Triple
T16508181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Wilson |
E400984
|
entity |
| Predicate | playsRoleInBand |
P118484
|
FINISHED |
| Object | bass guitarist of Snow Patrol |
—
|
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: bass guitarist of Snow Patrol | Statement: [Paul Wilson, playsRoleInBand, bass guitarist of Snow Patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRoleInBand Context triple: [Paul Wilson, playsRoleInBand, bass guitarist of Snow Patrol]
-
A.
hasRoleInBand
chosen
Indicates that an entity holds a specific role or position within a band.
-
B.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
usesBand
Indicates that one entity employs or makes use of a particular band (such as a group, frequency band, or band resource) in performing an action or fulfilling a function.
-
D.
workedAsSessionMusicianFor
Indicates that one entity performed as a session musician providing musical services or recordings for another entity, typically an artist, band, or production.
-
E.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54331c8190b3c4f9de95cbbc5e |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.