Triple
T30651206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slow Drag |
E780263
|
entity |
| Predicate | oftenDancedIn |
P184382
|
FINISHED |
| Object | juke joints |
—
|
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: juke joints | Statement: [Slow Drag, oftenDancedIn, juke joints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDancedIn Context triple: [Slow Drag, oftenDancedIn, juke joints]
-
A.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
B.
hasDancePerformancesBy
Indicates that one entity features or includes dance performances carried out by another entity.
-
C.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
D.
usedInDance
Indicates that something is employed or incorporated as a component or element within a dance performance or practice.
-
E.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
- F. None of above. chosen
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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 29, 2026, 8:30 p.m.