Triple

T18638327
Position Surface form Disambiguated ID Type / Status
Subject Southampton urban area E455614 entity
Predicate hasPart P35 FINISHED
Object Woolston 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: Woolston | Statement: [Southampton urban area, hasPart, Woolston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Woolston
Context triple: [Southampton urban area, hasPart, Woolston]
  • A. Woolston chosen
    Woolston is a district of Southampton in Hampshire, England, historically known for its shipbuilding and marine engineering industries.
  • B. Woolston
    Woolston is a riverside suburb of Christchurch, New Zealand, known historically for its industrial activity and proximity to the Heathcote River.
  • C. Wollescote
    Wollescote is a suburban area of Stourbridge in the West Midlands, England, known for its residential character and proximity to local parks and green spaces.
  • D. Worston
    Worston is a small rural village and civil parish in Lancashire, England, situated within the Ribble Valley district.
  • E. Waddon
    Waddon is a suburban area in south London, England, known for its residential character, local shopping streets, and proximity to Croydon town centre.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54fcac2d48190a15ce8cc8e175198 completed April 19, 2026, 9:57 p.m.
Created at: April 10, 2026, 11:47 a.m.