Triple
T8786731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playing for Time |
E209059
|
entity |
| Predicate | isPianoDriven |
P85375
|
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: [Playing for Time, isPianoDriven, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPianoDriven Context triple: [Playing for Time, isPianoDriven, true]
-
A.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
B.
isNonVocalInstrumental
Indicates that an entity produces instrumental sound without involving vocalization.
-
C.
hasPianos
Indicates that one entity possesses, contains, or includes one or more pianos in relation to another entity.
-
D.
isInstrumental
Indicates that one entity serves as the means, tool, or instrument by which another entity performs an action or achieves an outcome.
-
E.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
- F. None of above. chosen
Provenance (4 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f76f27c819087aadf768df5adbf |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:43 p.m.