Triple
T3204796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If |
E67134
|
entity |
| Predicate | hasSignatureDanceRoutine |
P29261
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [If, hasSignatureDanceRoutine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureDanceRoutine Context triple: [If, hasSignatureDanceRoutine, true]
-
A.
hasDanceChoreography
chosen
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
B.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
C.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
D.
hasDanceQuality
Indicates that something possesses a particular characteristic or attribute related to dance, such as style, skill, or expressive quality.
-
E.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.