Triple
T18049995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Rawlings |
E431904
|
entity |
| Predicate | primaryPerformanceRole |
P6869
|
FINISHED |
| Object | lead guitarist |
—
|
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: lead guitarist | Statement: [David Rawlings, primaryPerformanceRole, lead guitarist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPerformanceRole Context triple: [David Rawlings, primaryPerformanceRole, lead guitarist]
-
A.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
B.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
C.
primaryPosition
chosen
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
D.
currentPrimaryRole
Indicates the role an entity is presently holding as its main or most important function or position.
-
E.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff4a6e08190a5ca8d191aa7f0ae |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.