Triple

T6706782
Position Surface form Disambiguated ID Type / Status
Subject Bislama E153026 entity
Predicate hasSecondLanguageSpeakers P27353 FINISHED
Object yes 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: yes | Statement: [Bislama, hasSecondLanguageSpeakers, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondLanguageSpeakers
Context triple: [Bislama, hasSecondLanguageSpeakers, yes]
  • A. secondLanguageSpeakers chosen
    Indicates that the referenced language is spoken as a second (non-native) language by the specified group or number of people.
  • B. hasSecondaryLanguage
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • C. hasSecondaryLanguageTradition
    Indicates that an entity possesses an additional, non-primary language tradition associated with it, such as in its use, documentation, or cultural context.
  • D. hasNativeSpeakers
    Indicates that a language or dialect is spoken as a first language by one or more people or populations.
  • E. isBilingual
    Indicates that an entity is able to communicate fluently in two distinct languages.
  • 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_69c68808d8d8819087369015270788fe completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d16897e48190b43eda2206b14d6a completed March 27, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69c6d089c7488190a00853fb12f53b2a completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:06 p.m.