Triple

T22951391
Position Surface form Disambiguated ID Type / Status
Subject Botatwe languages E570026 entity
Predicate haveWritingSystemsForSomeMembers P150359 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: [Botatwe languages, haveWritingSystemsForSomeMembers, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveWritingSystemsForSomeMembers
Context triple: [Botatwe languages, haveWritingSystemsForSomeMembers, true]
  • A. hasOfficialWritingSystem
    Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
  • B. hasWritingSystemForMajorLanguage
    Indicates that there exists a writing system used to represent a major language associated with the given entity.
  • C. writingSystemDevelopedFor
    Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
  • D. writingSystemUsedIn
    Indicates that a particular writing system is employed for written communication within a given language, region, or context.
  • E. isWrittenWith
    Indicates that something is created or expressed using a particular writing tool, medium, or system.
  • F. None of above. chosen

Provenance (4 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_69e2459199d08190a8184ee2aa935842 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181a285448190a718734fe933d51a completed April 29, 2026, 3:57 a.m.
PD Predicate disambiguation batch_69ef3b882e708190b0eb0c87021c75b8 completed April 27, 2026, 10:33 a.m.
PDg Predicate description generation batch_69ef538a115081908982597f79355840 completed April 27, 2026, 12:16 p.m.
Created at: April 17, 2026, 3:46 p.m.