Triple
T16437131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restless Heart |
E399205
|
entity |
| Predicate | originalIntention |
P6484
|
FINISHED |
| Object | David Coverdale solo album |
—
|
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: David Coverdale solo album | Statement: [Restless Heart, originalIntention, David Coverdale solo album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalIntention Context triple: [Restless Heart, originalIntention, David Coverdale solo album]
-
A.
originalMeaning
Indicates that something retains or conveys its initial, intended sense or significance, as opposed to a later or altered interpretation.
-
B.
originalIntendedStatus
Indicates the status that was initially planned or expected for an entity before any changes or updates occurred.
-
C.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
D.
originalReason
chosen
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
E.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba49f3481908e7ea62467ef5813 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.