Triple

T2500719
Position Surface form Disambiguated ID Type / Status
Subject East Jerusalem E52456 entity
Predicate otherCommonLanguage P12203 FINISHED
Object Hebrew 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: Hebrew | Statement: [East Jerusalem, otherCommonLanguage, Hebrew]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: otherCommonLanguage
Context triple: [East Jerusalem, otherCommonLanguage, Hebrew]
  • A. otherLanguage chosen
    Indicates that an entity has or uses an additional language distinct from its primary or main language.
  • B. isWidelySpokenIn
    Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
  • C. languagesSpoken
    Indicates that an entity is able to communicate using one or more specified languages.
  • D. languageEquivalent
    Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
  • E. secondLanguageSpeakers
    Indicates that the referenced language is spoken as a second (non-native) language by the specified group or number of people.
  • 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_69ab4957b3a88190adf968ae0c1b931c completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd1b144a481909b1f8d96742a92e7 completed March 7, 2026, 7:20 a.m.
PD Predicate disambiguation batch_69abd0bba5348190bb4637d3165cb339 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.