Triple

T21268212
Position Surface form Disambiguated ID Type / Status
Subject George James Symons E524185 entity
Predicate familyName P18 FINISHED
Object Symons NE NERFINISHED

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: Symons | Statement: [George James Symons, familyName, Symons]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Symons
Context triple: [George James Symons, familyName, Symons]
  • A. Symons chosen
    Symons is a surname most notably associated with Donald Symons, an influential evolutionary psychologist known for his work on human sexuality.
  • B. Sijmons
    Sijmons is a surname variant of Simons, commonly found in Dutch-speaking regions.
  • C. Simonds
    Simonds is a surname most notably associated with Canadian Lieutenant-General Guy Simonds, a prominent military commander during the Second World War.
  • D. Simmons
    Simmons is a common English-language surname borne by numerous notable individuals across fields such as entertainment, sports, academia, and business.
  • E. Simonis
    Simonis is a major Brussels Metro interchange station serving multiple lines in the northwest of Brussels, Belgium.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735ee38cc81909b4e7c5996bb64f9 completed April 21, 2026, 8:31 a.m.
Created at: April 16, 2026, 4 p.m.