Triple
T30238951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Deeds |
E768852
|
entity |
| Predicate | castMember |
P1668
|
FINISHED |
| Object |
Sally McKenzie
Sally McKenzie is an Australian actress known for her work in film, television, and theatre, including a role in the crime-comedy film "Dirty Deeds."
|
E1918878
|
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: Sally McKenzie | Statement: [Dirty Deeds, castMember, Sally McKenzie]
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: Sally McKenzie Triple: [Dirty Deeds, castMember, Sally McKenzie]
Generated description
Sally McKenzie is an Australian actress known for her work in film, television, and theatre, including a role in the crime-comedy film "Dirty Deeds."
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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6804d6ef081908267e0f6dc644557 |
completed | May 2, 2026, 10:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27be54170881909723169aac946e56 |
completed | June 9, 2026, 7:18 a.m. |
| NEDg | Description generation | batch_6a27c3eb78c4819082d460d3f9c7373a |
completed | June 9, 2026, 7:42 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a27c466a2848190955a18c5f36837c0 |
completed | June 9, 2026, 7:44 a.m. |
Created at: April 29, 2026, 7:38 p.m.