Triple
T31191276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free as a Bird |
E795186
|
entity |
| Predicate | pianoBy |
P85583
|
FINISHED |
| Object | Paul McCartney |
—
|
NE NERFINISHED |
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: Paul McCartney | Statement: [Free as a Bird, pianoBy, Paul McCartney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pianoBy Context triple: [Free as a Bird, pianoBy, Paul McCartney]
-
A.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
-
B.
hasPianoStyle
Indicates that one entity possesses, is associated with, or is characterized by a particular style or manner of piano playing.
-
C.
hasPianist
chosen
Indicates that an entity is associated with or features a pianist, typically specifying who performs the piano part in a work, event, or group.
-
D.
hasPianoRiff
Indicates that one entity features or contains a distinctive piano riff associated with another entity.
-
E.
firstPerformerPiano
Indicates that the referenced entity is the first (primary or earliest) performer on the piano in a given performance or musical context.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.