Triple
T21871508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Wakeman |
E540012
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wakeman |
—
|
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: Wakeman | Statement: [Rick Wakeman, familyName, Wakeman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wakeman Context triple: [Rick Wakeman, familyName, Wakeman]
-
A.
Wakeman
chosen
Wakeman is a small village in Huron County, Ohio, known for its rural character and location along the Vermilion River.
-
B.
Oliver Wakeman
Oliver Wakeman is an English keyboardist and composer best known for his work with progressive rock bands such as Yes and for being the son of renowned Yes keyboardist Rick Wakeman.
-
C.
Blackmore
Blackmore is an English surname borne by various notable individuals across fields such as science, music, and literature.
-
D.
Bruford
Bruford was a British jazz-fusion and progressive rock band led by drummer Bill Bruford, known for its complex compositions and virtuosic musicianship.
-
E.
Rick Wakeman
Rick Wakeman is an English keyboardist and composer best known for his virtuosic work with the progressive rock band Yes and his elaborate solo concept albums.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f3368d488190a37224b587858ab0 |
completed | April 28, 2026, 5:49 p.m. |
Created at: April 16, 2026, 6:58 p.m.