Triple
T36730358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willard Hewitt |
E907313
|
entity |
| Predicate | cannotDanceAtStartOf |
P186247
|
FINISHED |
| Object | Footloose (musical) |
—
|
NE NERFINISHED |
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: Footloose (musical) | Statement: [Willard Hewitt, cannotDanceAtStartOf, Footloose (musical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotDanceAtStartOf Context triple: [Willard Hewitt, cannotDanceAtStartOf, Footloose (musical)]
-
A.
freeDanceRequired
Indicates that performing or providing a free dance segment is mandatory in the given context or event.
-
B.
continuedToDanceDespite
Indicates that one entity kept dancing even though a particular condition, event, or obstacle occurred that might normally have caused them to stop.
-
C.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
usedInDance
Indicates that something is employed or incorporated as a component or element within a dance performance or practice.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.