Triple
T34351721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillebachsee |
E881597
|
entity |
| Predicate | primaryLanguageOfSurroundingArea |
P157178
|
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: [Hillebachsee, primaryLanguageOfSurroundingArea, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLanguageOfSurroundingArea Context triple: [Hillebachsee, primaryLanguageOfSurroundingArea, German]
-
A.
primaryLanguageArea
Indicates that a specified region or area is one where a particular language is predominantly used or officially recognized as primary.
-
B.
languageOfSurroundingCountry
Indicates that a language is the primary or commonly used language in the country surrounding a given place or region.
-
C.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
D.
dominantLocalLanguage
chosen
Indicates that one language is the primary or most widely used language within a specific local area or community.
-
E.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.