Triple

T5189392
Position Surface form Disambiguated ID Type / Status
Subject Ralph Bellamy E117112 entity
Predicate familyName P18 FINISHED
Object Bellamy E257517 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: Bellamy | Statement: [Ralph Bellamy, familyName, Bellamy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bellamy
Context triple: [Ralph Bellamy, familyName, Bellamy]
  • A. Bellamy chosen
    Bellamy is a surname of English and French origin borne by various notable individuals across fields such as sports, politics, and the arts.
  • B. Myles
    Myles is a masculine given name of English origin, historically associated with figures such as Mayflower military leader Myles Standish.
  • C. Clyne
    Clyne is a village in Neath Port Talbot, Wales, situated near the community of Resolven in the Vale of Neath.
  • D. Beyton
    Beyton is a small rural village and civil parish in the English county of Suffolk, known for its traditional village green and historic buildings.
  • E. Romiley
    Romiley is a suburban village and residential area within the Metropolitan Borough of Stockport in Greater Manchester, England.
  • 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_69bd44620ff48190bcac01782107a397 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79c732b48190af62dfffcbc5e3a6 completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69bee08dfe648190a98b5a61f857d593 completed March 21, 2026, 6:16 p.m.
Created at: March 20, 2026, 1:46 p.m.