Triple

T1883854
Position Surface form Disambiguated ID Type / Status
Subject Aberdeenshire E39914 entity
Predicate recognisedLanguage P238 FINISHED
Object Scots LITERAL 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: Scots | Statement: [Aberdeenshire, recognisedLanguage, Scots]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognisedLanguage
Context triple: [Aberdeenshire, recognisedLanguage, Scots]
  • A. recognizedLanguage chosen
    Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
  • B. recognizedRegionalLanguage
    Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
  • C. recognizedAsDistinctLanguageFrom
    Indicates that one language is formally acknowledged or treated as a separate and distinct language from another, rather than as a dialect or variant of it.
  • D. isLanguageOf
    Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
  • E. isWorkingLanguageOf
    Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
  • F. None of above.

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_69a88633e4fc8190b7eb40463e048ec5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb4f53f408190ae30e1a12721e7d7 completed March 7, 2026, 5:17 a.m.
PD Predicate disambiguation batch_69abafe497a88190a1da6af2888b71b4 completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:34 p.m.