Triple

T3275158
Position Surface form Disambiguated ID Type / Status
Subject Southport E68739 entity
Predicate nearbySettlement P350 FINISHED
Object Preston E24766 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: Preston | Statement: [Southport, nearbySettlement, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [Southport, nearbySettlement, Preston]
  • A. Preston chosen
    Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
  • B. Preston
    Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
  • C. Manchester–Preston
    Manchester–Preston is a key railway corridor in North West England linking the city of Manchester with Preston and serving as part of the region’s intercity and commuter network.
  • D. Corby
    Corby is a town in Northamptonshire, England, known for its steel industry heritage and significant Scottish community.
  • E. Bradford
    Bradford is a major city in West Yorkshire, Northern England, known for its industrial heritage, diverse population, and role in the wool and textile industries.
  • 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_69ad859b54f881909bf530d549caf2fd completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adaff8a440819092509bc8511b2785 completed March 8, 2026, 5:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2e841d5588190a53ba90a46721b0f completed March 12, 2026, 4:22 p.m.
Created at: March 8, 2026, 3:10 p.m.