Triple
T28331424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waltzes |
E717546
|
entity |
| Predicate | danceOrigin |
P163496
|
FINISHED |
| Object | derived from ballroom waltz |
—
|
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: derived from ballroom waltz | Statement: [Waltzes, danceOrigin, derived from ballroom waltz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceOrigin Context triple: [Waltzes, danceOrigin, derived from ballroom waltz]
-
A.
danceOrigin
chosen
Indicates that one entity is the place, culture, or context where a particular dance style or form originally developed or emerged.
-
B.
danceCreated
Indicates that one entity is the creator or choreographer of a particular dance or dance work.
-
C.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
D.
danceDirection
Indicates the direction or orientation in which the dancing action is performed or moves.
-
E.
recognizedAsClassicalDanceBy
Indicates that one entity is acknowledged or accepted by another entity as belonging to the tradition or category of classical dance.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bce044c81908c397f6eb05e74c1 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:32 a.m.