Triple
T36342583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steam Heat |
E894969
|
entity |
| Predicate | notableChoreographyBy |
P204829
|
FINISHED |
| Object | Bob Fosse |
E135041
|
NE 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: Bob Fosse | Statement: [Steam Heat, notableChoreographyBy, Bob Fosse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChoreographyBy Context triple: [Steam Heat, notableChoreographyBy, Bob Fosse]
-
A.
notableDance
Indicates that the subject is especially recognized or distinguished for a particular dance or dancing performance.
-
B.
notableDanceSection
Indicates that a specific segment or portion of a performance is recognized as a particularly significant or distinguished dance section.
-
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.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
E.
choreographyIncludes
Indicates that a choreography or dance piece contains or incorporates a specific movement, sequence, or component as part of its structure.
- F. None of above. chosen
Provenance (5 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b42757248190be9f2c4209387733 |
completed | June 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.