Triple

T38459649
Position Surface form Disambiguated ID Type / Status
Subject Cristuru Secuiesc E912414 entity
Predicate locallyUsedLanguage P115774 FINISHED
Object Hungarian 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: Hungarian | Statement: [Cristuru Secuiesc, locallyUsedLanguage, Hungarian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locallyUsedLanguage
Context triple: [Cristuru Secuiesc, locallyUsedLanguage, Hungarian]
  • A. localLanguageName
    Indicates the name of a language as it is written or referred to in its own local or native form.
  • B. dominantLocalLanguage
    Indicates that one language is the primary or most widely used language within a specific local area or community.
  • C. languageOfLocalization
    Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
  • D. languageUsedInLocality chosen
    Indicates that a particular language is used or spoken within a specific locality or geographic area.
  • E. localLanguageStatus
    Indicates the status or condition of a language as used within a specific local or regional context.
  • 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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd02680d948190a3463fb119ba8556 completed May 7, 2026, 9:21 p.m.
PD Predicate disambiguation batch_69fcf89c69b4819082bbc564bd15137d completed May 7, 2026, 8:39 p.m.
Created at: May 3, 2026, 4:31 p.m.