Triple

T726263
Position Surface form Disambiguated ID Type / Status
Subject Forfar E14731 entity
Predicate unitaryAuthority P3379 FINISHED
Object Angus E2212 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: Angus | Statement: [Forfar, unitaryAuthority, Angus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angus
Context triple: [Forfar, unitaryAuthority, Angus]
  • A. Angus chosen
    Angus is a historic county and region on the east coast of Scotland known for its rural landscapes, agriculture, and coastal towns.
  • B. Angus South
    Angus South is a Scottish Parliament constituency covering part of the Angus council area, including the town of Carnoustie.
  • C. Veluws
    Veluws is a Dutch Low Saxon dialect spoken in the Veluwe region of the Netherlands, closely related to other eastern Dutch dialects such as Achterhooks.
  • D. Limousin
    Limousin is a former administrative region in central France known for its rural landscapes, cattle breeding, and historic towns such as Limoges and Tulle.
  • E. Pinto
    Pinto is a municipality in the southern part of the Community of Madrid, Spain, known for its residential character and location near the region’s capital.
  • 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_69a4934c753c81909b309027e48b9b3a completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a5a9adf08190bf2baade7e2e1c1c completed March 1, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a66d936bbc81908708ee5d0fc82100 completed March 3, 2026, 5:11 a.m.
Created at: March 1, 2026, 7:37 p.m.