Triple

T9720103
Position Surface form Disambiguated ID Type / Status
Subject Culloden, Scotland E235440 entity
Predicate locatedNear P294 FINISHED
Object Inverness E50911 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: Inverness | Statement: [Culloden, Scotland, locatedNear, Inverness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inverness
Context triple: [Culloden, Scotland, locatedNear, Inverness]
  • A. Inverness chosen
    Inverness is a city in the Scottish Highlands that serves as a major cultural and administrative center for the region.
  • B. Inverness
    Inverness is a small coastal community in Marin County, California, known for its scenic setting along Tomales Bay near Point Reyes National Seashore.
  • C. Nairn
    Nairn is a coastal town in the Highland council area of Scotland, known as a seaside resort on the Moray Firth.
  • 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. Greenock
    Greenock is a historic port town and former shipbuilding center on the River Clyde in western 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_69ca84d0123c819096f9dc3b6abb0881 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e419c2c8190b325d5fd692c6000 completed April 1, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f70597c81909d461b3d935b02a5 completed April 4, 2026, 11:32 p.m.
Created at: March 30, 2026, 8:20 p.m.