Triple
T37278101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Music in Motion |
E924702
|
entity |
| Predicate | hasPrimaryBandLeader |
P56624
|
FINISHED |
| Object | Jason Marsalis |
E270704
|
NE 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: Jason Marsalis | Statement: [Music in Motion, hasPrimaryBandLeader, Jason Marsalis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryBandLeader Context triple: [Music in Motion, hasPrimaryBandLeader, Jason Marsalis]
-
A.
hasBandLeaderRoleOf
Indicates that one entity serves in the role of band leader for another entity (typically a band or musical group).
-
B.
bandLeader
chosen
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
C.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
D.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
E.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
- F. None of above.
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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd3e466481908340ec289ebc4491 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.