Triple

T16711422
Position Surface form Disambiguated ID Type / Status
Subject Hedon E406114 entity
Predicate hasPostTown P2711 FINISHED
Object HULL E18246 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: HULL | Statement: [Hedon, hasPostTown, HULL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HULL
Context triple: [Hedon, hasPostTown, HULL]
  • A. Hull
    Hull is a small coastal town in eastern Massachusetts known for its beaches and seaside community on a narrow peninsula.
  • B. Hull
    Hull is a former city in western Quebec, Canada, that once stood on the north shore of the Ottawa River and is now part of the amalgamated city of Gatineau.
  • C. Hull chosen
    Hull, formally known as Kingston upon Hull, is a port city in East Yorkshire, England, noted for its maritime heritage and role as a major North Sea trading hub.
  • D. Hull
    Hull is a common English surname borne by various notable individuals across politics, sports, and the arts.
  • E. Port of Hull
    The Port of Hull is a major commercial seaport on the Humber Estuary in eastern England, serving as an important hub for cargo handling, passenger ferries, and maritime trade.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e386523fc08190a13a4232af191992 completed April 18, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a515ca7c8190a2d5894f4273f9c8 completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:20 a.m.