Triple
T21419581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levitate |
E528398
|
entity |
| Predicate | hasImprovisationalElements |
P63181
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Levitate, hasImprovisationalElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImprovisationalElements Context triple: [Levitate, hasImprovisationalElements, true]
-
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.
hasImprovisationFrom
Indicates that something includes or is derived from an improvisational performance or source.
-
C.
hasImprovisationStyle
Indicates that an entity exhibits or is associated with a particular style or manner of improvisation.
-
D.
isImprovisational
Indicates that an action, performance, or behavior is created spontaneously in the moment rather than being pre-planned or scripted.
-
E.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2ccddc08190b4f66fa6ccda41e2 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:47 p.m.