Triple

T28505079
Position Surface form Disambiguated ID Type / Status
Subject Xubuntu E721345 entity
Predicate supportsMultilingual P11998 FINISHED
Object true 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: true | Statement: [Xubuntu, supportsMultilingual, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsMultilingual
Context triple: [Xubuntu, supportsMultilingual, true]
  • A. isMultilingual
    Indicates that an entity can understand and/or communicate in multiple languages.
  • B. supportsInternationalization chosen
    Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
  • C. secondaryLanguageSupport
    Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
  • D. hasMultilingualPresence
    Indicates that an entity maintains an active presence or representation in multiple languages.
  • E. usesLanguageSupport
    Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
  • 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_69f01a5c072081908c7b04bcf6478da9 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_6a00b03a50a88190bfb95cdcfc6142a2 completed May 10, 2026, 4:20 p.m.
PD Predicate disambiguation batch_6a00afe55f248190b2cb4c7e62cc3ffc completed May 10, 2026, 4:18 p.m.
Created at: April 28, 2026, 3:09 a.m.