Triple
T34993721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alistair Petrie |
E1009463
|
entity |
| Predicate | portrayedCharacter |
P1668
|
FINISHED |
| Object |
Sandy Langbourne
Sandy Langbourne is a fictional character played by British actor Alistair Petrie, known from his work in film and television.
|
E2120195
|
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: Sandy Langbourne | Statement: [Alistair Petrie, portrayedCharacter, Sandy Langbourne]
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: Sandy Langbourne Triple: [Alistair Petrie, portrayedCharacter, Sandy Langbourne]
Generated description
Sandy Langbourne is a fictional character played by British actor Alistair Petrie, known from his work in film and television.
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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f784c0d06881908e951686d681658f |
completed | May 3, 2026, 5:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b28b75e48190848542bd083179d8 |
completed | June 21, 2026, 9:44 a.m. |
| NEDg | Description generation | batch_6a37b35f30b48190a2ef8bf97859463a |
completed | June 21, 2026, 9:48 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a37b47166f48190a351377c2080628e |
completed | June 21, 2026, 9:52 a.m. |
Created at: May 3, 2026, 4:01 p.m.