Triple
T29435122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banky Edwards |
E746548
|
entity |
| Predicate | roleInCreativeWork |
P15464
|
FINISHED |
| Object | inker of Bluntman and Chronic |
—
|
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: inker of Bluntman and Chronic | Statement: [Banky Edwards, roleInCreativeWork, inker of Bluntman and Chronic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCreativeWork Context triple: [Banky Edwards, roleInCreativeWork, inker of Bluntman and Chronic]
-
A.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
B.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
notableWorkRole
chosen
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: April 28, 2026, 3:16 p.m.