Triple

T3442589
Position Surface form Disambiguated ID Type / Status
Subject Finnish Sign Language E72598 entity
Predicate hasCorpus P32304 FINISHED
Object video corpora collected by Finnish researchers 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: video corpora collected by Finnish researchers | Statement: [Finnish Sign Language, hasCorpus, video corpora collected by Finnish researchers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCorpus
Context triple: [Finnish Sign Language, hasCorpus, video corpora collected by Finnish researchers]
  • A. hasCorpusType
    Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
  • B. corpus chosen
    Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
  • C. hasLimitedCorpus
    Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
  • D. hasCorollary
    Indicates that one statement, result, or proposition follows as a corollary from another, typically more general, statement.
  • E. primaryCorpusType
    Indicates the main or dominant type or category of corpus associated with an entity.
  • 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.