Triple
T5441316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struttin’ with Some Barbecue |
E122138
|
entity |
| Predicate | frequentlyPerformedIn |
P11801
|
FINISHED |
| Object | traditional jazz repertoire |
—
|
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: traditional jazz repertoire | Statement: [Struttin’ with Some Barbecue, frequentlyPerformedIn, traditional jazz repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlyPerformedIn Context triple: [Struttin’ with Some Barbecue, frequentlyPerformedIn, traditional jazz repertoire]
-
A.
frequentlyPerformedAt
Indicates that an action or event occurs regularly or with high frequency at a particular location or context.
-
B.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
C.
frequentlyRecordedBy
Indicates that an entity is often documented, captured, or logged by a particular agent, system, or recording process.
-
D.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.