Triple

T13910995
Position Surface form Disambiguated ID Type / Status
Subject Erik Coomes E334492 entity
Predicate familyName P18 FINISHED
Object Coomes E334492 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: Coomes | Statement: [Erik Coomes, familyName, Coomes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coomes
Context triple: [Erik Coomes, familyName, Coomes]
  • A. Coomes chosen
    Coomes is the surname of Erik "E-Bass" Coomes, an American bassist known for his work with the band Lettuce and various hip-hop and funk artists.
  • B. Cohon
    Cohon is the family surname of American actor, author, and narrator Peter Coyote, born Peter Cohon.
  • C. CoMo
    CoMo is a common nickname for Columbia, Missouri, a mid-sized college town known for the University of Missouri and its vibrant arts and music scene.
  • D. Cunningham
    Cunningham is a common Scottish surname borne by numerous notable individuals across fields such as technology, politics, sports, and the arts.
  • E. Coe
    Coe is a surname most prominently associated with Sebastian Coe, the British middle-distance running champion and influential sports administrator.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2723461881908376b5509ee0d530 completed April 14, 2026, 11:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c72879e48190ac01d0a2023b098c completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:16 p.m.