Triple
T28920061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turk 182 |
E733483
|
entity |
| Predicate | screenwriter |
P2831
|
FINISHED |
| Object |
Denis Hamill
Denis Hamill is an American journalist, novelist, and screenwriter known for his gritty New York–set stories and work in film and print media.
|
E1839099
|
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: Denis Hamill | Statement: [Turk 182, screenwriter, Denis Hamill]
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: Denis Hamill Triple: [Turk 182, screenwriter, Denis Hamill]
Generated description
Denis Hamill is an American journalist, novelist, and screenwriter known for his gritty New York–set stories and work in film and print media.
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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b19e61481909162ff801e90d95b |
completed | May 2, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d41d69188190a3a8b43a6649662d |
completed | June 7, 2026, 2:14 a.m. |
| NEDg | Description generation | batch_6a24d848273c8190b82c01f4138965af |
completed | June 7, 2026, 2:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a24dc4d0e24819096fe1d44c1e72446 |
completed | June 7, 2026, 2:49 a.m. |
Created at: April 28, 2026, 8:18 a.m.