Triple

T21467893
Position Surface form Disambiguated ID Type / Status
Subject Corbridge E529640 entity
Predicate hasPostTown P2711 FINISHED
Object CORBRIDGE 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: CORBRIDGE | Statement: [Corbridge, hasPostTown, CORBRIDGE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CORBRIDGE
Context triple: [Corbridge, hasPostTown, CORBRIDGE]
  • A. Corbridge chosen
    Corbridge is a historic village in Northumberland, England, known for its Roman heritage and picturesque setting on the banks of the River Tyne.
  • B. Curbridge
    Curbridge is a small rural village in Oxfordshire, England, situated within the district of West Oxfordshire.
  • C. Curbridge
    Curbridge is a small village in Hampshire, England, situated near the River Hamble and known for its rural character and riverside setting.
  • D. Robertsbridge
    Robertsbridge is a historic village in East Sussex, England, known for its medieval origins and rural setting in the Rother district.
  • E. Creebridge
    Creebridge is a small settlement in Dumfries and Galloway, Scotland, situated on the River Cree near the town of Newton Stewart.
  • 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_69e0c459acb481909bb6ee452a0045c7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9f415d48190a2b0993a4f3c018f completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:15 p.m.