Triple

T837861
Position Surface form Disambiguated ID Type / Status
Subject Raleigh E18109 entity
Predicate hasSisterCity P919 FINISHED
Object Kingston upon 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: Kingston upon Hull | Statement: [Raleigh, hasSisterCity, Kingston upon Hull]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kingston upon Hull
Context triple: [Raleigh, hasSisterCity, Kingston upon 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. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • D. King's Lynn
    King's Lynn is a historic market and port town in Norfolk, England, known for its medieval architecture and long-standing role as a regional commercial center.
  • E. Huddersfield
    Huddersfield is a large market town in West Yorkshire, England, known for its Victorian architecture, university, and role in the Industrial Revolution.
  • 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_69a49389f44881909a608fb27d89f247 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4abd0e8bc8190afe29cd4745c2f86 completed March 1, 2026, 9:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3b99a6c08190995ece1c1e9a54c9 completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:38 p.m.