Triple
T29332015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandralekha (1948 film) |
E743804
|
entity |
| Predicate | drumDanceSequenceFeatures |
P103855
|
FINISHED |
| Object | large number of dancers |
—
|
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: large number of dancers | Statement: [Chandralekha (1948 film), drumDanceSequenceFeatures, large number of dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drumDanceSequenceFeatures Context triple: [Chandralekha (1948 film), drumDanceSequenceFeatures, large number of dancers]
-
A.
danceFeature
chosen
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
B.
dancePattern
Indicates a recurring or structured way in which an entity performs or organizes a dance or sequence of dance movements.
-
C.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
-
D.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
E.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689bdf748190ae27cdae897bc6b3 |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:29 p.m.