Triple
T33793763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freiburg |
E866007
|
entity |
| Predicate | primaryGermanName |
P25775
|
FINISHED |
| Object | Freiburg im Üechtland |
E866007
|
NE 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: Freiburg im Üechtland | Statement: [Freiburg, primaryGermanName, Freiburg im Üechtland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGermanName Context triple: [Freiburg, primaryGermanName, Freiburg im Üechtland]
-
A.
pluralGermanName
Indicates that the given name is the correct German plural form of a singular term.
-
B.
nameInGerman
Indicates that an entity is known or referred to by a specific name in the German language.
-
C.
firstHolderNameInGerman
Indicates that the relationship specifies the name of the first holder expressed in the German language.
-
D.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
-
E.
primaryName
chosen
Indicates that the associated name is the main or most commonly used name for the entity in question.
- F. None of above.
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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405108e5c881908ebf0bf830d3e152 |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.