Triple
T29807385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace for Drowning |
E756873
|
entity |
| Predicate | hasContributingMusician |
P130621
|
FINISHED |
| Object | Nick Beggs |
—
|
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: Nick Beggs | Statement: [Grace for Drowning, hasContributingMusician, Nick Beggs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContributingMusician Context triple: [Grace for Drowning, hasContributingMusician, Nick Beggs]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
hasBandMemberAsComposer
Indicates that a band has one of its own members serving as the composer of a musical work.
-
C.
hasBackingMusiciansFrom
Indicates that an artist or musical act is supported or accompanied by backing musicians who originate from a specified place or group.
-
D.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
E.
hasMusicalPersonnel
chosen
Indicates a relationship where an entity is associated with specific musical personnel who perform, contribute to, or are involved in its musical activities or productions.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: April 29, 2026, 5:22 p.m.