Triple
T29458283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JackBoys |
E747157
|
entity |
| Predicate | mainArtistCollective |
P166201
|
FINISHED |
| Object | Cactus Jack Records roster |
—
|
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: Cactus Jack Records roster | Statement: [JackBoys, mainArtistCollective, Cactus Jack Records roster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainArtistCollective Context triple: [JackBoys, mainArtistCollective, Cactus Jack Records roster]
-
A.
artistCollective
chosen
Indicates a relationship where multiple artists are organized or associated together as a collaborative group or collective.
-
B.
coArtist
Indicates that two or more entities collaborate together as artists on the same creative work or project.
-
C.
performerEnsemble
Indicates a relationship where an individual performer is associated with, or is a member of, a musical or artistic ensemble.
-
D.
notableArtistGroup
Indicates that an artist is a member of, or significantly associated with, a particular artist group or collective.
-
E.
artistsFrom
Indicates that one or more artists originate from, are associated with, or come from a specified place or region.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 3:47 p.m.