Triple

T9908291
Position Surface form Disambiguated ID Type / Status
Subject A921 road E185072 entity
Predicate passesThrough P225 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: [A921 road, passesThrough, Kinghorn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kinghorn
Context triple: [A921 road, passesThrough, 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. Kinghorn
    Kinghorn is a small rural community within the Township of King in Ontario, Canada, known for its historic character and countryside setting.
  • C. Auchtermuchty
    Auchtermuchty is a small historic town in Fife, Scotland, known for its medieval street layout and traditional Scottish character.
  • D. Knockbreck
    Knockbreck is a small rural settlement on the Waternish peninsula of the Isle of Skye in the Scottish Highlands.
  • E. Buchan
    Buchan is a Scottish surname and place name, often associated with the historic region of Buchan in Aberdeenshire, Scotland.
  • 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_69ca8296165881908ca4750701af1f29 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb50feb008190aa9c084f590c0ebd completed April 2, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69d228a405908190ad63ebd659779ed7 completed April 5, 2026, 9:17 a.m.
Created at: March 30, 2026, 8:41 p.m.