Triple

T1581797
Position Surface form Disambiguated ID Type / Status
Subject James Howe Jr. E33779 entity
Predicate familyName P18 FINISHED
Object Howe E34373 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: Howe | Statement: [James Howe Jr., familyName, Howe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Howe
Context triple: [James Howe Jr., familyName, Howe]
  • A. Howe chosen
    Howe is an English-language surname of Anglo-Norman and Old English origin, borne by numerous notable figures across politics, the military, the arts, and sports.
  • B. Hayes
    Hayes is a suburban district in southeast London, England, known for its residential character and green spaces within the London Borough of Bromley.
  • C. Harbison
    Harbison is a surname most notably associated with American composer John Harbison, known for his contributions to contemporary classical music.
  • D. Ledeacker
    Ledeacker is a small village in the Dutch province of North Brabant, now part of the municipality of Land van Cuijk.
  • E. Farguson
    Farguson is an alternative spelling of the surname Ferguson, which is of Scottish origin.
  • 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_69a885f27a4c8190a4622252cdf54c00 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa6213b6a481908f321d1468be436d completed March 6, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad403355f4819084a560226a190b8a completed March 8, 2026, 9:24 a.m.
Created at: March 4, 2026, 7:27 p.m.