Triple

T19824388
Position Surface form Disambiguated ID Type / Status
Subject Hobokan E476281 entity
Predicate alternativeNameOf P39 FINISHED
Object Hobuck NE NERFINISHED

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: Hobuck | Statement: [Hobokan, alternativeNameOf, Hobuck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hobuck
Context triple: [Hobokan, alternativeNameOf, Hobuck]
  • A. Hobuck chosen
    Hobuck is the original settlement name that preceded the modern city of Hoboken, New Jersey.
  • B. Buckman
    Buckman is a historic, mixed-use neighborhood in inner southeast Portland, Oregon, known for its older residential streets, industrial areas, and vibrant local businesses.
  • C. Hobkin
    Hobkin is a relatively uncommon surname that appears to be a variant or related form of the English surname Hopkin.
  • D. Hibler
    Hibler is a surname most notably associated with Winston Hibler, an American screenwriter, producer, and narrator known for his work on Walt Disney nature documentaries and animated films.
  • E. Corbitt
    Corbitt is a variant spelling of the surname Corbett, which is of English and Scottish origin.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e655017c188190ae9e17ae6b0eee05 completed April 20, 2026, 4:32 p.m.
Created at: April 10, 2026, 1:50 p.m.