Triple

T12737483
Position Surface form Disambiguated ID Type / Status
Subject Frindsbury shipyard E304399 entity
Predicate locatedIn P40 FINISHED
Object Frindsbury E766615 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: Frindsbury | Statement: [Frindsbury shipyard, locatedIn, Frindsbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frindsbury
Context triple: [Frindsbury shipyard, locatedIn, Frindsbury]
  • A. Frindsbury chosen
    Frindsbury is a residential area and historic parish forming part of the town of Strood in Medway, Kent, England.
  • B. Oldbury
    Oldbury is a town in the West Midlands of England that serves as the administrative centre of the Metropolitan Borough of Sandwell.
  • C. Aldbury
    Aldbury is a picturesque historic village in Hertfordshire, England, known for its traditional cottages, village pond, and scenic Chilterns countryside setting.
  • D. Parwich
    Parwich is a small rural village in the Derbyshire Peak District of England, noted for its traditional stone buildings and scenic countryside setting.
  • E. Wraysbury
    Wraysbury is a village and civil parish in Berkshire, England, situated near the River Thames and known for its historic sites and proximity to Windsor.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9646cfcac81909283dca987755c0e completed April 10, 2026, 8:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c8ff57c8190a935b5c9f4bb5aa3 completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:26 p.m.