Triple

T844437
Position Surface form Disambiguated ID Type / Status
Subject Kingston upon Hull E18246 entity
Predicate hasShortName P1354 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: [Kingston upon Hull, hasShortName, Hull]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hull
Context triple: [Kingston upon Hull, hasShortName, Hull]
  • A. 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.
  • B. Hartlepool
    Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
  • C. Leeds
    Leeds is a major city in West Yorkshire, England, known as a key commercial, cultural, and educational center in the north of the country.
  • D. Southampton
    Southampton is a major port city on England’s south coast, historically significant for its maritime trade, shipbuilding, and role as a departure point for transatlantic voyages.
  • E. South Shields
    South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
  • 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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac09249c8190a8099b94a3c9e2cc completed March 1, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4bfac5cc8190a5fba1c5da98391d completed March 7, 2026, 4:02 p.m.
Created at: March 1, 2026, 7:38 p.m.