Triple
T34008136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Brers in A Minor |
E872018
|
entity |
| Predicate | showcasesBand |
P104302
|
FINISHED |
| Object | The Allman Brothers Band classic lineup |
—
|
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: The Allman Brothers Band classic lineup | Statement: [Les Brers in A Minor, showcasesBand, The Allman Brothers Band classic lineup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showcasesBand Context triple: [Les Brers in A Minor, showcasesBand, The Allman Brothers Band classic lineup]
-
A.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
B.
showcasesAt
Indicates that something is presented, exhibited, or displayed at a particular place, event, or context.
-
C.
isAboutBand
Indicates that something (such as a work, discussion, or reference) concerns or focuses on a musical band.
-
D.
showcasesBandSensibilities
chosen
Indicates that something highlights or exemplifies the characteristic style, strengths, or musical identity of a band.
-
E.
bandNameInShow
Indicates that a particular band name is used or appears within a specific show.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.