Triple
T5188607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Gideon |
E117091
|
entity |
| Predicate | choreographs |
P11856
|
FINISHED |
| Object | dance numbers |
—
|
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: dance numbers | Statement: [Joe Gideon, choreographs, dance numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choreographs Context triple: [Joe Gideon, choreographs, dance numbers]
-
A.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
-
B.
choreographicApproach
Indicates an artistic relationship where one entity defines or employs a particular method, style, or strategy for creating or organizing choreography in relation to another.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
choreographer
chosen
Indicates that one entity is the person who designs and arranges the dance or movement sequences performed by another entity.
-
E.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c56280819085926316f7b520bc |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.