Triple

T16063716
Position Surface form Disambiguated ID Type / Status
Subject Cleo Hampton E389677 entity
Predicate familyName P18 FINISHED
Object Hampton E389684 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: Hampton | Statement: [Cleo Hampton, familyName, Hampton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hampton
Context triple: [Cleo Hampton, familyName, Hampton]
  • A. Hampton
    Hampton is a suburban town in the London Borough of Richmond upon Thames, England, situated on the north bank of the River Thames.
  • B. Hampton
    Hampton is an independent coastal city in southeastern Virginia known for its historic role in early American settlement and its location at the entrance to the Chesapeake Bay.
  • C. Hampton
    Hampton is a historic coastal town in southeastern New Hampshire, known as one of the colony’s earliest settlements and now a popular beach community.
  • D. Hampton chosen
    Hampton is a surname of English origin borne by various notable individuals, including those in the arts and public life.
  • E. Hampton
    Hampton is a suburban railway station in Melbourne, Australia, serving the bayside suburb of Hampton on the city’s Sandringham line.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1837b048881908326739bbede756f completed April 17, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe47ca9748190be24a490c3cf0e8c completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:57 a.m.