Triple

T13648981
Position Surface form Disambiguated ID Type / Status
Subject Charles Walter Allfrey E326678 entity
Predicate familyName P18 FINISHED
Object Allfrey E326678 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: Allfrey | Statement: [Charles Walter Allfrey, familyName, Allfrey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Allfrey
Context triple: [Charles Walter Allfrey, familyName, Allfrey]
  • A. Allfrey chosen
    Allfrey is an English surname borne by various notable individuals, including military figures and writers.
  • B. Fargus
    Fargus is a central playable character in the comedic fantasy action-platformer game Pandemonium!, known for his quirky personality and magical abilities.
  • C. Alfege
    Alfege is an Anglo-Saxon saint and Archbishop of Canterbury, venerated for his martyrdom after refusing to allow a ransom to be paid for his release from Viking captors.
  • D. Alfrick
    Alfrick is a small rural village and civil parish in Worcestershire, England, situated near the Malvern Hills.
  • E. Aylett
    Aylett is an English-language surname borne by various individuals, including historical and contemporary figures.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc608466c81908f6d2c9c92cc86aa completed April 12, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d44e2148190a279aa6d103bf204 completed May 3, 2026, 7:08 p.m.
Created at: April 9, 2026, 9:52 p.m.