Triple
T29801964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liturgy |
E756729
|
entity |
| Predicate | createdOnDancer |
P195185
|
FINISHED |
| Object | Wendy Whelan |
—
|
NE NERFINISHED |
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, createdOnDancer, Wendy Whelan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdOnDancer Context triple: [Liturgy, createdOnDancer, Wendy Whelan]
-
A.
danceCreated
Indicates that one entity is the creator or choreographer of a particular dance or dance work.
-
B.
associatedDanceCreator
Indicates that a dance is created, choreographed, or otherwise brought into existence by a particular creator.
-
C.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
D.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
- F. None of above. chosen
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_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: April 29, 2026, 5:18 p.m.