Triple

T17774047
Position Surface form Disambiguated ID Type / Status
Subject Scottish inland waterways network E443718 entity
Predicate connects P390 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: [Scottish inland waterways network, connects, Inverness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inverness
Context triple: [Scottish inland waterways network, connects, Inverness]
  • A. Inverness
    Inverness is a small coastal community in Marin County, California, known for its scenic setting along Tomales Bay near Point Reyes National Seashore.
  • B. Inverness
    Inverness is a small coastal locality within Queensland’s Capricorn Coast region in Australia.
  • C. Inverness chosen
    Inverness is a city in the Scottish Highlands that serves as a major cultural and administrative center for the region.
  • 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4871af4248190aed2b3bd42433771 completed April 19, 2026, 7:41 a.m.
Created at: April 10, 2026, 10:12 a.m.