Triple
T2657800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Party |
E54655
|
entity |
| Predicate | hasRecordingArtistRole |
P9640
|
FINISHED |
| Object | lead vocals by Ricky Nelson |
—
|
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: lead vocals by Ricky Nelson | Statement: [Garden Party, hasRecordingArtistRole, lead vocals by Ricky Nelson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingArtistRole Context triple: [Garden Party, hasRecordingArtistRole, lead vocals by Ricky Nelson]
-
A.
hasArtistRole
chosen
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
C.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
D.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
E.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94c61a08190bdf5e1caeff3e788 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.