Triple

T20897797
Position Surface form Disambiguated ID Type / Status
Subject Kingskettle E514585 entity
Predicate hasPostTown P2711 FINISHED
Object Cupar NE NERFINISHED

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: Cupar | Statement: [Kingskettle, hasPostTown, Cupar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cupar
Context triple: [Kingskettle, hasPostTown, Cupar]
  • A. Cupar chosen
    Cupar is a historic market town in eastern Scotland that once served as the county town of Fife.
  • B. Dunfermline
    Dunfermline is a historic Scottish town and former royal capital known for its medieval abbey and rich cultural heritage.
  • C. Gartcosh
    Gartcosh is a village in North Lanarkshire, Scotland, historically known for its steelworks and now part of the Greater Glasgow commuter belt.
  • D. Arbirlot
    Arbirlot is a small rural village in the Angus council area of eastern Scotland, known for its historic parish church and scenic countryside setting near the North Sea coast.
  • E. Tyndrum
    Tyndrum is a small village in the Scottish Highlands that serves as a key road and rail junction for travelers heading to western and northern Scotland.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4f7ebe48190952a85547a0f31a1 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e8f826788190b11008cc94b2a4e4 completed April 21, 2026, 3:03 a.m.
Created at: April 16, 2026, 12:47 p.m.