Triple

T21966494
Position Surface form Disambiguated ID Type / Status
Subject Moray Firth coast E542471 entity
Predicate hasTown P847 FINISHED
Object Inverness 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: Inverness | Statement: [Moray Firth coast, hasTown, Inverness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inverness
Context triple: [Moray Firth coast, hasTown, 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. Inverness
    Inverness is a small coastal locality within Queensland’s Capricorn Coast region in Australia.
  • D. Nairn
    Nairn is a coastal town in the Highland council area of Scotland, known as a seaside resort on the Moray Firth.
  • E. 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.
  • 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1245b821c8190816058c2a07707a3 completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.