Triple

T16864539
Position Surface form Disambiguated ID Type / Status
Subject Bridge of Orchy E410004 entity
Predicate near P350 FINISHED
Object Tyndrum 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: Tyndrum | Statement: [Bridge of Orchy, near, Tyndrum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tyndrum
Context triple: [Bridge of Orchy, near, Tyndrum]
  • A. Tyndrum chosen
    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.
  • B. 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.
  • C. Cupar
    Cupar is a historic market town in eastern Scotland that once served as the county town of Fife.
  • D. Alyth
    Alyth is a small historic town in eastern Perthshire, Scotland, known for its scenic setting near the Highlands and its traditional stone architecture.
  • E. Maybole
    Maybole is a historic small town in South Ayrshire, Scotland, traditionally regarded as the capital of the Carrick district.
  • 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b505a390819097ec31cd210eca60 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:24 a.m.