Triple
T34798668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juke Joint Festival |
E1003156
|
entity |
| Predicate | regionCultureFeatured |
P1968
|
FINISHED |
| Object | Mississippi Delta |
—
|
NE NERFINISHED |
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: Mississippi Delta | Statement: [Juke Joint Festival, regionCultureFeatured, Mississippi Delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCultureFeatured Context triple: [Juke Joint Festival, regionCultureFeatured, Mississippi Delta]
-
A.
culturalGroupFeatured
Indicates that a particular cultural group is prominently highlighted, showcased, or given special attention in a context, event, or medium.
-
B.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
C.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
D.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
E.
ethnicCultureDocumented
Indicates that information about an ethnic culture has been recorded, described, or otherwise documented.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 3, 2026, 3:59 p.m.