Triple

T5655070
Position Surface form Disambiguated ID Type / Status
Subject central Fife E124596 entity
Predicate contains P35 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: [central Fife, contains, Kinghorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kinghorn
Context triple: [central Fife, contains, 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. Knockbreck
    Knockbreck is a small rural settlement on the Waternish peninsula of the Isle of Skye in the Scottish Highlands.
  • D. Buchan
    Buchan is a Scottish surname and place name, often associated with the historic region of Buchan in Aberdeenshire, Scotland.
  • E. Craighorn
    Craighorn is a hill in central Scotland located near the town of Alva in Clackmannanshire, popular with local walkers for its accessible ascent and scenic views.
  • 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_69c0082774a481909d7e63fb2aad56ac completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022f998688190b18eb6469e8c054f completed March 22, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04d9b43288190b6d7c610546b52f2 completed March 22, 2026, 8:14 p.m.
Created at: March 22, 2026, 3:42 p.m.