Triple
T5140372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Fancy |
E115931
|
entity |
| Predicate | danceAssociation |
P20189
|
FINISHED |
| Object | contra dance figures |
—
|
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: contra dance figures | Statement: [Portland Fancy, danceAssociation, contra dance figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceAssociation Context triple: [Portland Fancy, danceAssociation, contra dance figures]
-
A.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
B.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
C.
associatedDanceTrend
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
D.
danceForm
chosen
Indicates that one entity is a style or type of dance associated with the other entity.
-
E.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.