Triple

T17383570
Position Surface form Disambiguated ID Type / Status
Subject שירות הביטחון הכללי E422629 entity
Predicate שפה_רשמית P236 FINISHED
Object עברית 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: עברית | Statement: [שירות הביטחון הכללי, שפה_רשמית, עברית]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: שפה_רשמית
Context triple: [שירות הביטחון הכללי, שפה_רשמית, עברית]
  • A. officialLanguage chosen
    Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
  • B. shareOfficialLanguage
    Indicates that two entities have at least one official language in common.
  • C. standardLanguageOf
    Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
  • D. languageOfLetters
    Indicates that one entity is the language in which the other entity’s letters or written correspondence are composed.
  • E. officialLanguageUse
    Indicates that a particular language is formally designated and used by an authority (such as a government or institution) for official communication, documentation, or functions.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a87d9948190986021f1fb5a4e00 completed April 19, 2026, 2:14 a.m.
PD Predicate disambiguation batch_69e3b02ac8688190a7182f1b2151d721 completed April 18, 2026, 4:24 p.m.
Created at: April 10, 2026, 5:45 a.m.