Triple

T4837943
Position Surface form Disambiguated ID Type / Status
Subject Broseley E108106 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Barrow E184032 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: Barrow | Statement: [Broseley, hasNeighbouringSettlement, Barrow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barrow
Context triple: [Broseley, hasNeighbouringSettlement, Barrow]
  • A. Barrow
    Barrow is a village and civil parish in the county of Suffolk in eastern England.
  • B. Barrow chosen
    Barrow is a small village and civil parish in Lancashire, England, situated within the Ribble Valley district.
  • C. Barrow
    Barrow is the former English name of Utqiaġvik, a remote Arctic coastal city in northern Alaska known as one of the northernmost settlements in the United States.
  • D. Thurso
    Thurso is a coastal town in the far north of Scotland, known as a gateway to the Highlands and a popular spot for surfing and access to the Orkney Islands.
  • E. Blyth
    Blyth is a coastal town and port in southeast Northumberland, England, known historically for coal mining and shipbuilding.
  • 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_69bd43fbe444819085cb970706ef73f7 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ce2e810819089f9a3f2a7574d44 completed March 20, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5cc054ac819099d6d3dbf415e710 completed March 21, 2026, 8:54 a.m.
Created at: March 20, 2026, 1:25 p.m.