Triple

T7558337
Position Surface form Disambiguated ID Type / Status
Subject Orfordness E178729 entity
Predicate locatedNear P294 FINISHED
Object Orford E37398 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: Orford | Statement: [Orfordness, locatedNear, Orford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orford
Context triple: [Orfordness, locatedNear, Orford]
  • A. Orford Quay
    Orford Quay is a small historic waterfront and landing area on the River Ore serving the village of Orford in Suffolk, England.
  • B. Orford, Suffolk chosen
    Orford, Suffolk is a historic coastal village in eastern England known for its medieval castle, former port, and scenic setting on the River Ore.
  • C. Orfordness
    Orfordness is a remote shingle spit on the Suffolk coast of England that became a key site for early radar experiments and later secret military testing.
  • D. Thorpeness
    Thorpeness is a quirky seaside village on the Suffolk coast of England, known for its mock-Tudor holiday homes, boating Meare, and the iconic House in the Clouds.
  • E. Alnmouth
    Alnmouth is a coastal village in Northumberland, England, known for its scenic beach, historic harbor, and role as a small railway stop on the route between Newcastle and Edinburgh.
  • 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_69c69f2da22c8190a50942ac20af70e8 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f8db3d508190850ed41854d69838 completed March 27, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c856c833288190842c41e9010d56de completed March 28, 2026, 10:31 p.m.
Created at: March 27, 2026, 3:50 p.m.