Triple

T640878
Position Surface form Disambiguated ID Type / Status
Subject Great Andamanese E16735 entity
Predicate currentLinguaFranca P237 FINISHED
Object mixed Great Andamanese language 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: mixed Great Andamanese language | Statement: [Great Andamanese, currentLinguaFranca, mixed Great Andamanese language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: currentLinguaFranca
Context triple: [Great Andamanese, currentLinguaFranca, mixed Great Andamanese language]
  • A. isWidelySpokenIn
    Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
  • B. deFactoLanguage chosen
    Indicates that a language is used in practice as the primary or common language in a context, even if it has no official legal status there.
  • C. languagesSpoken
    Indicates that an entity is able to communicate using one or more specified languages.
  • D. majorityLanguageOf
    Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
  • E. regionLanguage
    Indicates that a particular language is used or officially recognized within a specific geographic region.
  • 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_69a4936be1c88190af56540324b57da7 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49f0189b08190a584b744f36fa761 completed March 1, 2026, 8:18 p.m.
PD Predicate disambiguation batch_69a49d0830008190a26ee158ed4dd1fe completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:36 p.m.