Triple
T483991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzigane |
E9832
|
entity |
| Predicate | hasDanceQuality |
P13505
|
FINISHED |
| Object | showpiece |
—
|
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: showpiece | Statement: [Tzigane, hasDanceQuality, showpiece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceQuality Context triple: [Tzigane, hasDanceQuality, showpiece]
-
A.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
stateDance
Indicates a relationship where a state is associated with or designates an official dance.
-
C.
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.
-
D.
nationalDance
Indicates that a particular dance is officially recognized as the national dance of a country or nation.
-
E.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0ba310c81909645ef7e8a20b52f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.