Triple
T22089327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindy Hop |
E545870
|
entity |
| Predicate | danceRoleTerminology |
P32690
|
FINISHED |
| Object | lead |
—
|
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: lead | Statement: [Lindy Hop, danceRoleTerminology, lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceRoleTerminology Context triple: [Lindy Hop, danceRoleTerminology, lead]
-
A.
danceRole
chosen
Indicates that one entity has a specific role or function within a dance performed with or in relation to another entity.
-
B.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
C.
theatricalMovement
Indicates a relationship where an entity is associated with, participates in, or exemplifies a particular theatrical movement or style within the performing arts.
-
D.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
E.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e47ba08190a208af72a7cc176f |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.