Triple
T35915251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg Gallery |
E1038725
|
entity |
| Predicate | primaryArtistFeatured |
P7867
|
FINISHED |
| Object | Jim Brandenburg |
E2162373
|
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: Jim Brandenburg | Statement: [Brandenburg Gallery, primaryArtistFeatured, Jim Brandenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArtistFeatured Context triple: [Brandenburg Gallery, primaryArtistFeatured, Jim Brandenburg]
-
A.
primaryArtist
chosen
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
B.
hasFeaturedArtist
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
-
C.
leadSingleFeaturing
Indicates that an artist is featured on the lead single of another artist’s release.
-
D.
secondaryArtist
Indicates that an entity participates in a creative work as an additional or supporting artist, rather than as the primary artist.
-
E.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific artist).
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6f3b9348190937c431261b62113 |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.