Triple

T21572330
Position Surface form Disambiguated ID Type / Status
Subject APT-E E532313 entity
Predicate preservedLocation P2249 FINISHED
Object Shildon 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: Shildon | Statement: [APT-E, preservedLocation, Shildon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shildon
Context triple: [APT-E, preservedLocation, Shildon]
  • A. Shildon chosen
    Shildon is a town in County Durham, England, historically significant as a cradle of the railway industry and home to major railway heritage attractions.
  • B. Didlington
    Didlington is a small village in Norfolk, England, known for its rural landscape, historic estate, and proximity to the River Wissey.
  • C. 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.
  • D. Benwell
    Benwell is a residential district in the west end of Newcastle upon Tyne, England, known for its historical industrial roots and subsequent urban regeneration.
  • E. Morpeth
    Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative 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_69e0c460db088190828c64206a450273 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eee9cd50188190b44eb25fb87312bb completed April 27, 2026, 4:45 a.m.
Created at: April 16, 2026, 6:30 p.m.