Triple
T31448612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilio |
E802255
|
entity |
| Predicate | notableForDancers |
P207428
|
FINISHED |
| Object | showcase role for male virtuosity |
—
|
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: showcase role for male virtuosity | Statement: [Basilio, notableForDancers, showcase role for male virtuosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForDancers Context triple: [Basilio, notableForDancers, showcase role for male virtuosity]
-
A.
notableDance
Indicates that the subject is especially recognized or distinguished for a particular dance or dancing performance.
-
B.
notableDanceSection
Indicates that a specific segment or portion of a performance is recognized as a particularly significant or distinguished dance section.
-
C.
notableBallet
Indicates that there is a notable or significant ballet associated with the subject.
-
D.
featuredDancers
Indicates that certain dancers are highlighted or given special prominence in a performance, event, or context.
-
E.
notableFlyGirlDancer
Indicates that a person is recognized as a prominent or distinguished member of the Fly Girls dance group.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 9:11 p.m.