Triple
T20346899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Godfather of Punk |
E495894
|
entity |
| Predicate | hasRoleTarget |
P14889
|
FINISHED |
| Object | singer |
—
|
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: singer | Statement: [The Godfather of Punk, hasRoleTarget, singer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleTarget Context triple: [The Godfather of Punk, hasRoleTarget, singer]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
D.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
E.
requiresRole
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783937a48190ac86e4959a781a2b |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.