Triple
T29801980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liturgy |
E756729
|
entity |
| Predicate | associatedDancer |
P86188
|
FINISHED |
| Object | Wendy Whelan |
E208391
|
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: Wendy Whelan | Statement: [Liturgy, associatedDancer, Wendy Whelan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDancer Context triple: [Liturgy, associatedDancer, Wendy Whelan]
-
A.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
B.
dancePartner
Indicates that two entities are engaged in or paired together for a dance.
-
C.
associatedDanceCreator
Indicates that a dance is created, choreographed, or otherwise brought into existence by a particular creator.
-
D.
hasDanceAssociation
chosen
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
E.
performingPartner
Indicates that one entity is the partner who participates in or carries out a performance together with another entity.
- F. None of above.
Provenance (4 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2721dbcb78819096ab3e5f7b005789 |
completed | June 8, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:18 p.m.