Triple

T8437475
Position Surface form Disambiguated ID Type / Status
Subject Moray Firth E199264 entity
Predicate adjacentTo P224 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: [Moray Firth, adjacentTo, Inverness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inverness
Context triple: [Moray Firth, adjacentTo, 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_69ca8314cd6c8190a6b8c2a1096e18f3 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe13446788190ad52a4fd6e8b498a completed March 31, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecc3c0d508190bc0c7bd89f040967 completed April 2, 2026, 8:06 p.m.
Created at: March 30, 2026, 6:08 p.m.