Triple
T6624552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brackenheim |
E149761
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object |
Hausen an der Zaber
Hausen an der Zaber is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
|
E599932
|
NE FINISHED |
How this triple was built (4 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: Hausen an der Zaber | Statement: [Brackenheim, hasSubdivision, Hausen an der Zaber]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hausen an der Zaber Context triple: [Brackenheim, hasSubdivision, Hausen an der Zaber]
-
A.
Hausen an der Würm
Hausen an der Würm is a village and district of the town Weil der Stadt in the German state of Baden-Württemberg.
-
B.
Hausen
Hausen is a small suburban district of the town of Herbrechtingen in the state of Baden-Württemberg, Germany.
-
C.
Haus am Horn
Haus am Horn is a pioneering early Bauhaus model house in Weimar, Germany, designed in 1923 to showcase modernist architecture and functional living.
-
D.
Weisbachsches Haus
Weisbachsches Haus is a notable historic building and architectural landmark located in the city of Plauen, Germany.
-
E.
Waidhaus
Waidhaus is a municipality in eastern Bavaria, Germany, near the Czech border, known as a key road border crossing and transport hub.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hausen an der Zaber Triple: [Brackenheim, hasSubdivision, Hausen an der Zaber]
Generated description
Hausen an der Zaber is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Hausen an der Zaber Target entity description: Hausen an der Zaber is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
-
A.
Hausen an der Würm
Hausen an der Würm is a village and district of the town Weil der Stadt in the German state of Baden-Württemberg.
-
B.
Hausen
Hausen is a small suburban district of the town of Herbrechtingen in the state of Baden-Württemberg, Germany.
-
C.
Haus am Horn
Haus am Horn is a pioneering early Bauhaus model house in Weimar, Germany, designed in 1923 to showcase modernist architecture and functional living.
-
D.
Weisbachsches Haus
Weisbachsches Haus is a notable historic building and architectural landmark located in the city of Plauen, Germany.
-
E.
Waidhaus
Waidhaus is a municipality in eastern Bavaria, Germany, near the Czech border, known as a key road border crossing and transport hub.
- F. None of above. chosen
Provenance (5 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6af7fc054819099a2e58cefd8fed7 |
completed | March 27, 2026, 4:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbe690548190a771bb1ec8d3aacf |
completed | March 27, 2026, 6:26 p.m. |
| NEDg | Description generation | batch_69c6cd0a98908190a5725c49bad7589d |
completed | March 27, 2026, 6:31 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c6cdcc10c08190aa98212bd17063a3 |
completed | March 27, 2026, 6:34 p.m. |
Created at: March 27, 2026, 1:58 p.m.