Triple
T23595505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All That Music & More Festival |
E582602
|
entity |
| Predicate | hasTypeOfPerformer |
P35860
|
FINISHED |
| Object | popular musical acts |
—
|
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: popular musical acts | Statement: [All That Music & More Festival, hasTypeOfPerformer, popular musical acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPerformer Context triple: [All That Music & More Festival, hasTypeOfPerformer, popular musical acts]
-
A.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
hasPerformerFamily
Indicates that an entity has a family member who performs or participates as a performer in relation to that entity.
-
C.
hasPerformerCharacteristic
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
D.
hasPerformerGroupType
Indicates that an entity is associated with a performer group of a specific type or category (e.g., band, choir, ensemble).
-
E.
hasMusicalArtistType
chosen
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08f9b648190b90d3b2aa49ba85e |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.