Triple

T4459068
Position Surface form Disambiguated ID Type / Status
Subject Kinghorn Golf Club E98205 entity
Predicate locatedIn P40 FINISHED
Object Kinghorn E17765 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: Kinghorn | Statement: [Kinghorn Golf Club, locatedIn, Kinghorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kinghorn
Context triple: [Kinghorn Golf Club, locatedIn, Kinghorn]
  • A. Kinghorn chosen
    Kinghorn is a coastal town in Fife, Scotland, situated on the north shore of the Firth of Forth and known historically as a royal burgh and seaside resort.
  • B. Auchtermuchty
    Auchtermuchty is a small historic town in Fife, Scotland, known for its medieval street layout and traditional Scottish character.
  • C. Buchan
    Buchan is a Scottish surname and place name, often associated with the historic region of Buchan in Aberdeenshire, Scotland.
  • D. Culdrose
    Culdrose is a locality in Cornwall, England, best known as the site of the Royal Naval Air Station Culdrose.
  • E. Arkinholm
    Arkinholm is a historic site in southern Scotland best known as the location of a decisive 1455 battle that helped end the power of the Black Douglas family.
  • 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_69b3454a7c608190944f5455c8031d73 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3567184f481908a2787e4ac9bb345 completed March 13, 2026, 12:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69b65f3b9950819085c285defda52d51 completed March 15, 2026, 7:26 a.m.
Created at: March 12, 2026, 11:33 p.m.