Triple

T3442563
Position Surface form Disambiguated ID Type / Status
Subject Finnish Sign Language E72598 entity
Predicate hasOwnGrammar P12378 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: [Finnish Sign Language, hasOwnGrammar, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOwnGrammar
Context triple: [Finnish Sign Language, hasOwnGrammar, true]
  • A. hasGrammar
    Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
  • B. hasKnownGrammar
    Indicates that an entity is associated with a grammar whose structure and rules are already defined or understood.
  • C. hasDistinctGrammar chosen
    Indicates that the subject’s grammar system is different in structure or rules from that of the object.
  • D. hasOwnPhonology
    Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
  • E. hasGrammarDifferenceFrom
    Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
  • 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_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.
Created at: March 8, 2026, 3:16 p.m.