Triple
T2025189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Bavaria |
E44191
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Ebersberg
Ebersberg is a small Bavarian town and district capital east of Munich, known for its surrounding forest and traditional Upper Bavarian character.
|
E251965
|
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: Ebersberg | Statement: [Upper Bavaria, contains, Ebersberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ebersberg Context triple: [Upper Bavaria, contains, Ebersberg]
-
A.
Hubersdorf
Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
-
B.
Altötting
Altötting is a Bavarian pilgrimage town renowned as one of Germany’s most important Catholic shrines, centered around the Chapel of Grace and its venerated Black Madonna.
-
C.
Pöcking
Pöcking is a municipality in Bavaria, Germany, located on the western shore of Lake Starnberg and known for its affluent residential character.
-
D.
Günsberg
Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
-
E.
Essling
Essling is a village near Vienna, Austria, historically notable as one of the sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
- 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: Ebersberg Triple: [Upper Bavaria, contains, Ebersberg]
Generated description
Ebersberg is a small Bavarian town and district capital east of Munich, known for its surrounding forest and traditional Upper Bavarian character.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ebersberg Target entity description: Ebersberg is a small Bavarian town and district capital east of Munich, known for its surrounding forest and traditional Upper Bavarian character.
-
A.
Hubersdorf
Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
-
B.
Altötting
Altötting is a Bavarian pilgrimage town renowned as one of Germany’s most important Catholic shrines, centered around the Chapel of Grace and its venerated Black Madonna.
-
C.
Pöcking
Pöcking is a municipality in Bavaria, Germany, located on the western shore of Lake Starnberg and known for its affluent residential character.
-
D.
Günsberg
Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
-
E.
Essling
Essling is a village near Vienna, Austria, historically notable as one of the sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f3faa08190a48ae1355d6e009f |
completed | March 7, 2026, 5:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae7ee977c08190a90355f510aa28f2 |
completed | March 9, 2026, 8:03 a.m. |
| NEDg | Description generation | batch_69ae7f90d3a88190bf61c6f063b67c06 |
completed | March 9, 2026, 8:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae800868948190a5504969c4cabb7d |
completed | March 9, 2026, 8:08 a.m. |
Created at: March 4, 2026, 7:38 p.m.