Triple
T36647152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero No.1 |
E904744
|
entity |
| Predicate | includesDanceNumbers |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDanceNumbers Context triple: [Hero No.1, includesDanceNumbers, yes]
-
A.
containsDanceNumber
chosen
Indicates that something (such as a work, performance, or production) includes at least one distinct dance sequence or dance number as part of its content.
-
B.
featuredInDanceNumbersWith
Indicates that two entities are prominently included together in one or more dance numbers within a performance or production.
-
C.
numberOfDances
Indicates the quantity or count of dances associated with a given entity or event.
-
D.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
-
E.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
- F. None of above.
Provenance (1 batch)
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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.