Triple

T484183
Position Surface form Disambiguated ID Type / Status
Subject Methil E9837 entity
Predicate near P350 FINISHED
Object Buckhaven E8174 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: Buckhaven | Statement: [Methil, near, Buckhaven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buckhaven
Context triple: [Methil, near, Buckhaven]
  • A. Buckhaven chosen
    Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
  • B. Hillington
    Hillington is a small village and civil parish in Norfolk, England, known for its rural setting and historic country estate, Hillington Hall.
  • C. Kingscliff
    Kingscliff is a coastal town in northeastern New South Wales, Australia, known for its beaches, surf breaks, and relaxed holiday atmosphere.
  • D. Morley
    Morley is a town in West Yorkshire, England, situated between Leeds and Bradford within the Leeds City Council metropolitan area.
  • E. Motherwell
    Motherwell is a former industrial town in North Lanarkshire, Scotland, historically known as a major center of the steel industry.
  • 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_69a2e802e2908190ab17c9479e0b6412 completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f0ba310c81909645ef7e8a20b52f completed Feb. 28, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69a49eb7b49c819098352f36d020cde7 completed March 1, 2026, 8:16 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.