Triple
T32324957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Love (guitar solo, with Wings) |
E825882
|
entity |
| Predicate | improvised |
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: [My Love (guitar solo, with Wings), improvised, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvised Context triple: [My Love (guitar solo, with Wings), improvised, true]
-
A.
isFrequentlyImprovisedOver
Indicates that one thing commonly serves as the underlying basis or structure over which improvisation is often performed.
-
B.
isImprovisational
Indicates that an action, performance, or behavior is created spontaneously in the moment rather than being pre-planned or scripted.
-
C.
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.
-
D.
in
Indicates that one entity is located within the spatial, temporal, or conceptual bounds of another entity.
-
E.
reasonForImprovisation
Indicates that one event, condition, or factor serves as the cause or motivation for an improvisational action or behavior.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde7cd8481908d3128d089c86c14 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:47 a.m.