Triple

T8573948
Position Surface form Disambiguated ID Type / Status
Subject Orford Quay E202997 entity
Predicate partOf P40 FINISHED
Object Orford waterfront E202997 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 waterfront | Statement: [Orford Quay, partOf, Orford waterfront]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orford waterfront
Context triple: [Orford Quay, partOf, Orford waterfront]
  • A. Orford Quay chosen
    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
    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. 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.
  • D. Pegwell Bay
    Pegwell Bay is a coastal inlet on the English Channel in Kent, England, noted for its mudflats, saltmarshes, and rich birdlife within a protected nature reserve.
  • E. 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.
  • 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_69ca8328ebe481909a8c038fa79959b4 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbea458c1081908e79bee2cbf97207 completed March 31, 2026, 3:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea88464b88190983e22e70bf38e63 completed April 2, 2026, 5:33 p.m.
Created at: March 30, 2026, 6:21 p.m.