Triple

T12094569
Position Surface form Disambiguated ID Type / Status
Subject Laurence Sharp E288035 entity
Predicate hasSurname P18 FINISHED
Object Sharp E52476 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: Sharp | Statement: [Laurence Sharp, hasSurname, Sharp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sharp
Context triple: [Laurence Sharp, hasSurname, Sharp]
  • A. Sharp chosen
    Sharp is a common English surname borne by numerous notable individuals across politics, sports, academia, and the arts.
  • B. Sharp
    Sharp is a Japanese electronics manufacturer best known for producing consumer devices such as mobile phones, televisions, and display technologies.
  • C. Sharpness
    Sharpness is a small port village in Gloucestershire, England, situated on the River Severn and known historically as a key inland dock and terminus for canal traffic.
  • D. Blunt
    Blunt is an English surname borne by various notable figures in the arts, politics, and public life.
  • E. Quick
    Quick is a character associated with the boxer and entertainer Sugar Ray, likely appearing in media or promotional contexts connected to his persona.
  • 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_69d6ab4964708190850585628b287b0c completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d91550ce508190babf5755e1553734 completed April 10, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f66edf7881908f29b5b40b9d020f completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.