Triple
T29707730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alien |
E751680
|
entity |
| Predicate | performerOfKeyboards |
P12601
|
FINISHED |
| Object | Jordan Rudess |
—
|
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: Jordan Rudess | Statement: [The Alien, performerOfKeyboards, Jordan Rudess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerOfKeyboards Context triple: [The Alien, performerOfKeyboards, Jordan Rudess]
-
A.
notableKeyboardist
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
B.
associatedInstrumentalist
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
-
C.
playedInstrument
chosen
Indicates that an entity performed or used a particular musical instrument.
-
D.
firstPerformerPiano
Indicates that the referenced entity is the first (primary or earliest) performer on the piano in a given performance or musical context.
-
E.
keyboardsBy
Indicates that one entity is the creator, manufacturer, or provider of keyboards 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 28, 2026, 7:28 p.m.