Triple
T30023199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Cross |
E762804
|
entity |
| Predicate | roleInKingCrimson |
P135541
|
FINISHED |
| Object | violinist and keyboardist |
—
|
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: violinist and keyboardist | Statement: [David Cross, roleInKingCrimson, violinist and keyboardist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKingCrimson Context triple: [David Cross, roleInKingCrimson, violinist and keyboardist]
-
A.
roleInMotörhead
Indicates the specific role or function an entity has within the band Motörhead.
-
B.
roleInMegadeth
Indicates that one entity holds or has held a specific role or position within the band Megadeth in relation to the other entity.
-
C.
roleInScorpions
Indicates the specific function or position an entity holds within the group or context referred to as "Scorpions."
-
D.
musicalEnsembleRole
chosen
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
E.
roleInGuitarHero
Indicates the specific function or part an entity has within the context of the Guitar Hero game (e.g., player role, character role, or gameplay position).
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: April 29, 2026, 6:48 p.m.