Triple

T2062982
Position Surface form Disambiguated ID Type / Status
Subject British Sign Language E45832 entity
Predicate hasFingerspellingSystem P26215 FINISHED
Object two-handed manual alphabet 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: two-handed manual alphabet | Statement: [British Sign Language, hasFingerspellingSystem, two-handed manual alphabet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFingerspellingSystem
Context triple: [British Sign Language, hasFingerspellingSystem, two-handed manual alphabet]
  • A. usesFingerspellingSystem chosen
    Indicates that one entity employs or applies a particular fingerspelling system in communication or representation.
  • B. languageOfSignage
    Indicates the language used on signs or written displays associated with an entity.
  • C. hasSyllabary
    Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
  • D. hasVowelSystem
    Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
  • E. hasPhoneme
    Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
  • 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_69a8891b38288190abd572ccad9b6928 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb9d239b48190a9f303446cbe3aa6 completed March 7, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69abb7aee9b48190999620176e3a6ee2 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:40 p.m.