Triple
T22793626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westfalen |
E564180
|
entity |
| Predicate | dominantModernLanguage |
P149740
|
FINISHED |
| Object | German |
—
|
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 | Statement: [Westfalen, dominantModernLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantModernLanguage Context triple: [Westfalen, dominantModernLanguage, German]
-
A.
dominantMediaLanguage
Indicates that one language is the primary or most prevalent medium of communication used in a given media context or outlet.
-
B.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
-
C.
laterLanguageDominant
Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
-
D.
educationLanguageDominant
Indicates that one language is the primary or most influential language used in a person’s education.
-
E.
modernLanguageDescendant
Indicates that one language is a direct or indirect descendant of another language in the modern era.
- F. None of above. chosen
Provenance (4 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd751f081909c7907c96c9906ea |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:30 p.m.