Triple
T35394240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whispers in the Dark |
E1023026
|
entity |
| Predicate | producer |
P490
|
FINISHED |
| Object |
Michael Bregman
Michael Bregman is an American film producer known for his work on various feature films, particularly in the thriller and crime genres.
|
E2272210
|
NE 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: Michael Bregman | Statement: [Whispers in the Dark, producer, Michael Bregman]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Michael Bregman Triple: [Whispers in the Dark, producer, Michael Bregman]
Generated description
Michael Bregman is an American film producer known for his work on various feature films, particularly in the thriller and crime genres.
Provenance (5 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794fe3db08190a2469f2d2280262c |
completed | May 3, 2026, 6:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d62f66108190a932d74bafeeec41 |
completed | June 29, 2026, 2:19 a.m. |
| NEDg | Description generation | batch_6a41d6d79f9c8190ab63069d374deddd |
completed | June 29, 2026, 2:22 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a41d72f88fc8190b5194d82e21e2da3 |
completed | June 29, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:03 p.m.