Triple
T7717629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hüsker Dü |
E174926
|
entity |
| Predicate | roleOfBobMould |
P75740
|
FINISHED |
| Object | guitarist and vocalist |
—
|
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: guitarist and vocalist | Statement: [Hüsker Dü, roleOfBobMould, guitarist and vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfBobMould Context triple: [Hüsker Dü, roleOfBobMould, guitarist and vocalist]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
roleOfPeopleOnIt
chosen
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
-
E.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.