Triple

T3442598
Position Surface form Disambiguated ID Type / Status
Subject Finnish Sign Language E72598 entity
Predicate hasPhonologicalParameters P48839 FINISHED
Object handshape 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: handshape | Statement: [Finnish Sign Language, hasPhonologicalParameters, handshape]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhonologicalParameters
Context triple: [Finnish Sign Language, hasPhonologicalParameters, handshape]
  • A. hasPhonologicalType
    Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
  • B. hasPhoneme
    Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
  • C. hasOwnPhonology
    Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
  • D. hasPhonemicVowels
    Indicates that a language or linguistic system distinguishes vowel sounds as separate phonemes that can change word meaning.
  • E. hasPhonologicalBasisFor
    Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
  • 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_69ad85b05c848190b7a28ceec2bd7b74 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adba28ec448190a6a07c5f16235fe3 completed March 8, 2026, 6:04 p.m.
PD Predicate disambiguation batch_69adae0255b48190a9069f7871c7a012 completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb1ecb02881908394f197e31431b4 completed March 8, 2026, 5:29 p.m.
Created at: March 8, 2026, 3:16 p.m.