Triple

T1662772
Position Surface form Disambiguated ID Type / Status
Subject Lothian and Fife E35945 entity
Predicate containsTown P847 FINISHED
Object Cupar E21353 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: Cupar | Statement: [Lothian and Fife, containsTown, Cupar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cupar
Context triple: [Lothian and Fife, containsTown, 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. Balerno
    Balerno is a suburban village on the outskirts of Edinburgh, Scotland, known for its scenic setting near the Pentland Hills and its residential character.
  • D. Clackmannan
    Clackmannan is a small historic town in central Scotland that once served as the county town of Clackmannanshire.
  • E. Kirkcaldy
    Kirkcaldy is a coastal town on the east coast of Scotland, known historically for its linoleum industry and as one of the largest settlements in Fife.
  • 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_69a88606aa808190aa0b421b4271f220 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90ab5d1a08190a3325ff203b573fb completed March 5, 2026, 4:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb4c726c81909bc916e76bb0f96f completed March 13, 2026, 7:22 a.m.
Created at: March 4, 2026, 7:29 p.m.