Triple
T28378452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valse Hot |
E718816
|
entity |
| Predicate | involvesImprovisation |
P63181
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Valse Hot, involvesImprovisation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesImprovisation Context triple: [Valse Hot, involvesImprovisation, yes]
-
A.
hasImprovisation
chosen
Indicates that an entity includes, involves, or is characterized by improvisational elements or unscripted creative actions in relation to another entity or context.
-
B.
isImprovisational
Indicates that an action, performance, or behavior is created spontaneously in the moment rather than being pre-planned or scripted.
-
C.
hasImprovisationFrom
Indicates that something includes or is derived from an improvisational performance or source.
-
D.
reasonForImprovisation
Indicates that one event, condition, or factor serves as the cause or motivation for an improvisational action or behavior.
-
E.
hasImprovisationStyle
Indicates that an entity exhibits or is associated with a particular style or manner of improvisation.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 1:04 a.m.