Triple

T7616026
Position Surface form Disambiguated ID Type / Status
Subject Jägerndorf E172362 entity
Predicate historicalLanguageMajority P36041 FINISHED
Object German-speaking population 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: German-speaking population | Statement: [Jägerndorf, historicalLanguageMajority, German-speaking population]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalLanguageMajority
Context triple: [Jägerndorf, historicalLanguageMajority, German-speaking population]
  • A. hasMajorityLanguageHistorically chosen
    Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
  • B. historicalLanguage
    Indicates that one language is a historical or earlier form/ancestor of another language.
  • C. majorityLanguageOf
    Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
  • D. historicalLanguageStatus
    Indicates that a language had a particular official, social, or functional status during a past historical period.
  • E. historicalLanguageGroup
    Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
  • 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_69c6994f50808190ba228764bb422417 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fe73ff7c8190ab1218d97b37416d completed March 27, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69c6f4e725a88190b1f05dd224f7f4f2 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:55 p.m.