Triple

T15111140
Position Surface form Disambiguated ID Type / Status
Subject Edward Stephen Harkness E360913 entity
Predicate hasSurname P18 FINISHED
Object Harkness E360913 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: Harkness | Statement: [Edward Stephen Harkness, hasSurname, Harkness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harkness
Context triple: [Edward Stephen Harkness, hasSurname, Harkness]
  • A. Harkness chosen
    Harkness is a surname of Scottish origin borne by various notable individuals in fields such as business, philanthropy, and the arts.
  • B. Hazlemere
    Hazlemere is a suburban village and civil parish in Buckinghamshire, England, situated near High Wycombe.
  • C. Blackridge
    Blackridge is a village in West Lothian, Scotland, situated between Bathgate and Armadale with a largely residential and commuter community.
  • D. Moross
    Moross is a surname most notably associated with American composer Jerome Moross, known for his film and television scores and concert works.
  • E. Underhill
    Underhill is an English surname historically associated with various notable figures in politics, religion, and the arts.
  • 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_69d85a0491ec8190830960be8fafb994 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0058c04f481909deeac0271d961b6 completed April 15, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7eb139c8190b76393e4a8be576b completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:05 a.m.