Triple
T9247717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Baker |
E222238
|
entity |
| Predicate | hasWorkAttribute |
P73996
|
FINISHED |
| Object | musical comedy |
—
|
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: musical comedy | Statement: [Bob Baker, hasWorkAttribute, musical comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkAttribute Context triple: [Bob Baker, hasWorkAttribute, musical comedy]
-
A.
hasWorkAttributed
Indicates that a particular work or creation is credited or assigned as being produced by a specific agent or entity.
-
B.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
C.
hasWorkField
chosen
Indicates that an entity is associated with or operates within a particular field or area of work.
-
D.
hasWorkAsSetting
Indicates that a particular work (such as a story, film, or artwork) takes place in or uses a specified location, time, or environment as its setting.
-
E.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f55a848190a59e7087cc07f6ef |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.