Triple

T17106825
Position Surface form Disambiguated ID Type / Status
Subject Jaxen E415121 entity
Predicate hasOriginLanguageContext P21977 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: [Jaxen, hasOriginLanguageContext, English-speaking countries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOriginLanguageContext
Context triple: [Jaxen, hasOriginLanguageContext, English-speaking countries]
  • A. hasLanguageContext
    Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
  • B. originalLanguageContext chosen
    Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
  • C. hasLanguageOfOrigin
    Indicates that one entity has its origin or source in the language specified by another entity.
  • D. indirectOriginLanguage
    Indicates that something originates from a particular language, not directly but through one or more intermediate languages or sources.
  • E. nativeLanguageContext
    Indicates the relationship in which a language functions as the primary or native linguistic context for an entity’s communication or interpretation.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc2750b481908de18e8cb8f2195c completed April 18, 2026, 7:31 p.m.
PD Predicate disambiguation batch_69e35d6b1b988190a8d6b6fe78c35e59 completed April 18, 2026, 10:31 a.m.
Created at: April 10, 2026, 5:35 a.m.