Triple

T23878162
Position Surface form Disambiguated ID Type / Status
Subject Frederick Abberline E600123 entity
Predicate familyName P18 FINISHED
Object Abberline
Abberline is an English surname most notably associated with Frederick Abberline, the Victorian-era London police detective involved in the Jack the Ripper investigation.
E1604695 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: Abberline | Statement: [Frederick Abberline, familyName, Abberline]
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: Abberline
Triple: [Frederick Abberline, familyName, Abberline]
Generated description
Abberline is an English surname most notably associated with Frederick Abberline, the Victorian-era London police detective involved in the Jack the Ripper investigation.

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_69e295318e148190b9979d8fc02e168f completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cc032c9c81909986ae6f672c1ad1 completed April 29, 2026, 9:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f69c8c6808190b14117a0d67aba0e completed May 21, 2026, 8:23 p.m.
NEDg Description generation batch_6a0f6d4399e481908e08d9dc8dd5e139 completed May 21, 2026, 8:38 p.m.
NED2 Entity disambiguation (via description) batch_6a0f6e22305081909ad33dfaf65f004e completed May 21, 2026, 8:42 p.m.
Created at: April 17, 2026, 8:23 p.m.