Triple
T8954714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primate of Hungary |
E213443
|
entity |
| Predicate | titleLanguageOfLocal |
P38219
|
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: [Primate of Hungary, titleLanguageOfLocal, Hungarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleLanguageOfLocal Context triple: [Primate of Hungary, titleLanguageOfLocal, Hungarian]
-
A.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
B.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
C.
titleLanguageForm
chosen
Indicates the specific linguistic form or variant in which a title is expressed (e.g., language, script, or transliteration form).
-
D.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
E.
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).
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6724f3e4819092c6b13d80871e80 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.