Triple
T23359518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Man |
E593144
|
entity |
| Predicate | hasMoogSoloPerformedBy |
P63177
|
FINISHED |
| Object | Keith Emerson |
—
|
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: Keith Emerson | Statement: [Lucky Man, hasMoogSoloPerformedBy, Keith Emerson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoogSoloPerformedBy Context triple: [Lucky Man, hasMoogSoloPerformedBy, Keith Emerson]
-
A.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
-
B.
hasGuitarSolo
Indicates that an entity (such as a song or performance) contains or features a guitar solo.
-
C.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
D.
hasDrumSolo
Indicates that a musical performance, track, or section contains a featured solo passage played on drums.
-
E.
hasNotableSoloFor
chosen
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1a39988190b4b4993b80d5a5f6 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:30 p.m.