Triple
T25017492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhmerwald |
E626178
|
entity |
| Predicate | hasGermanNameFor |
P22792
|
FINISHED |
| Object | Bohemian Forest |
—
|
NE NERFINISHED |
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: Bohemian Forest | Statement: [Böhmerwald, hasGermanNameFor, Bohemian Forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGermanNameFor Context triple: [Böhmerwald, hasGermanNameFor, Bohemian Forest]
-
A.
nameInGerman
chosen
Indicates that an entity is known or referred to by a specific name in the German language.
-
B.
hasOfficialLanguageNameInGerman
Indicates that an entity has an official language name expressed specifically in the German language.
-
C.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
-
D.
hasTitleInGerman
Indicates that an entity has a specific title or name expressed in the German language.
-
E.
hasSorbianName
Indicates that an entity has a name or designation expressed in the Sorbian language.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:06 a.m.