Triple
T9391625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baryshnikov Arts Center |
E226037
|
entity |
| Predicate | artFormSupported |
P27458
|
FINISHED |
| Object | dance |
—
|
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 | Statement: [Baryshnikov Arts Center, artFormSupported, dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artFormSupported Context triple: [Baryshnikov Arts Center, artFormSupported, dance]
-
A.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
-
B.
artFormCreated
Indicates that one entity is the creator or originator of a particular artistic form, style, or genre associated with the other entity.
-
C.
hasArtFormPresented
chosen
Indicates that an entity presents, showcases, or features a particular art form.
-
D.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with another entity.
-
E.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510eae0c8190b7c4ab487a366bb3 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.