Triple
T36244394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoot |
E891616
|
entity |
| Predicate | associatedDanceName |
P204804
|
FINISHED |
| Object | Shoot dance |
E2175434
|
NE 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: Shoot dance | Statement: [Shoot, associatedDanceName, Shoot dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDanceName Context triple: [Shoot, associatedDanceName, Shoot dance]
-
A.
associatedDanceTrend
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
B.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
C.
associatedDanceCreator
Indicates that a dance is created, choreographed, or otherwise brought into existence by a particular creator.
-
D.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
E.
learnsToDanceIn
Indicates that an entity is in the process of acquiring or practicing dancing skills within a particular place or context.
- F. None of above. chosen
Provenance (5 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e04a33c81908288beb268abf51e |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.