Triple

T22211616
Position Surface form Disambiguated ID Type / Status
Subject John Kerr E548963 entity
Predicate familyName P18 FINISHED
Object Kerr E93876 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: Kerr | Statement: [John Kerr, familyName, Kerr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kerr
Context triple: [John Kerr, familyName, Kerr]
  • A. Kerr chosen
    Kerr is a surname of Scottish origin borne by numerous notable individuals across fields such as politics, academia, sports, and the arts.
  • B. Kerrh
    Kerrh is an alternative spelling variant of the name or term “Ker,” referring to the same underlying entity.
  • C. Ker
    Ker is a variant form of the surname Kerr, which is of Scottish origin and historically associated with Border Reiver families.
  • D. Ker
    Ker is a figure from Greek mythology personifying violent death and doom, often depicted as a malevolent spirit associated with battlefield slaughter.
  • E. Kaluza
    Kaluza is a surname most notably associated with Theodor Kaluza, the German physicist who proposed a unifying five-dimensional theory of gravity and electromagnetism.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2c8b608190b0047af4ac91b023 completed April 28, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0aa61ede44819090c46782098c5669 completed May 18, 2026, 5:39 a.m.
Created at: April 16, 2026, 8:36 p.m.