Triple

T2965075
Position Surface form Disambiguated ID Type / Status
Subject Highland council area E80141 entity
Predicate contains P35 FINISHED
Object Nairn E306292 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: Nairn | Statement: [Highland council area, contains, Nairn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nairn
Context triple: [Highland council area, contains, Nairn]
  • A. Nairn chosen
    Nairn is a coastal town in the Highland council area of Scotland, known as a seaside resort on the Moray Firth.
  • B. Huntly
    Huntly is a small town in New Zealand known for its coal mining history and location on the Waikato River between Hamilton and Auckland.
  • C. Huntly
    Huntly is a historic town in Aberdeenshire, Scotland, long associated with the Gordon family and the Marquess of Huntly.
  • D. Inveraray
    Inveraray is a historic town on the shores of Loch Fyne in western Scotland, noted for Inveraray Castle and its role as the traditional seat of the Dukes of Argyll.
  • E. Clackmannan
    Clackmannan is a small historic town in central Scotland that once served as the county town of Clackmannanshire.
  • 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_69ad8b1341848190bd19dbf46892887d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad995a28e88190a4d6b9ef2c0d8e61 completed March 8, 2026, 3:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69bde0234b6481908dcf37da32cf856b completed March 21, 2026, 12:02 a.m.
Created at: March 8, 2026, 2:58 p.m.