Triple

T16112243
Position Surface form Disambiguated ID Type / Status
Subject Carys E390907 entity
Predicate isUsedInLanguageContext P907 FINISHED
Object English-speaking countries 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: English-speaking countries | Statement: [Carys, isUsedInLanguageContext, English-speaking countries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUsedInLanguageContext
Context triple: [Carys, isUsedInLanguageContext, English-speaking countries]
  • A. hasLanguageContext
    Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
  • B. usedInLanguage chosen
    Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
  • C. isKnownInContextOf
    Indicates that an entity is recognized, relevant, or has significance specifically within a given context or domain.
  • D. isReleasedInContextOf
    Indicates that an entity is released or made available specifically within, or as part of, a particular context, situation, or framework.
  • E. hasLanguagePolicyContext
    Indicates that there is an associated language-related policy, rule, or regulatory context governing how language is used or managed in relation to the subject.
  • 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_69d87f1a8dd881909f1de6ef78849874 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e20167ee1481909e56dc632bfc0fc5 completed April 17, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69e1828518c48190a8ef3aaa46a1f639 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 5 a.m.