Triple

T8034248
Position Surface form Disambiguated ID Type / Status
Subject A484 road E187063 entity
Predicate connects P390 FINISHED
Object Burry Port E136348 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: Burry Port | Statement: [A484 road, connects, Burry Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burry Port
Context triple: [A484 road, connects, Burry Port]
  • A. Burry Port chosen
    Burry Port is a coastal town and port in southwest Wales known for its marina, sandy beaches, and links to Amelia Earhart’s historic transatlantic flight landing nearby.
  • B. Milborne Port
    Milborne Port was a former parliamentary borough in Somerset, England, that historically returned members to the House of Commons.
  • C. Warsop
    Warsop is a small town and civil parish in Nottinghamshire, England, historically linked to coal mining and situated near the larger market town of Mansfield.
  • D. Briton Ferry
    Briton Ferry is a town in South Wales situated near the mouth of the River Neath, historically known for its industrial heritage and docks.
  • E. Queenborough
    Queenborough is a small historic port town in Kent, England, situated on the Isle of Sheppey and known for its maritime heritage and medieval origins.
  • 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3ef50f4c8190a895ac301f182734 completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc56f493908190b68e791cdbe725fa completed March 31, 2026, 11:21 p.m.
Created at: March 30, 2026, 5:22 p.m.