Triple
T14348069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Hohenzollern |
E355778
|
entity |
| Predicate | traditionalLanguageOfUse |
P42338
|
FINISHED |
| Object | German language |
—
|
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 language | Statement: [Prince of Hohenzollern, traditionalLanguageOfUse, German language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLanguageOfUse Context triple: [Prince of Hohenzollern, traditionalLanguageOfUse, German language]
-
A.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
B.
languageFamilyTraditional
Indicates that one entity belongs to, or is classified under, the traditional language family of the other entity.
-
C.
typicalLanguages
chosen
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
D.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
E.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8d081c8190ac805726a3e98f4c |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.