Triple

T4822652
Position Surface form Disambiguated ID Type / Status
Subject Cupar railway station E107744 entity
Predicate locatedIn P40 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: [Cupar railway station, locatedIn, Cupar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cupar
Context triple: [Cupar railway station, locatedIn, 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. 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.
  • D. 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.
  • E. 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.
  • 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_69bd43f9efa081908314cb3e94fa1695 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6caa95ec8190bea525dbf3a00477 completed March 20, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf410bd6b08190a0ad4af6e5f4b0b8 completed March 22, 2026, 1:08 a.m.
Created at: March 20, 2026, 1:24 p.m.