Triple
T13659340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dietkirchen |
E326945
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Weilburg |
E145657
|
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: Weilburg | Statement: [Dietkirchen, locatedIn, Weilburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weilburg Context triple: [Dietkirchen, locatedIn, Weilburg]
-
A.
Weilburg
chosen
Weilburg is a historic town in the German state of Hesse, known for its Renaissance castle and as the ancestral seat of the House of Nassau-Weilburg.
-
B.
Limburg-Weilburg
Limburg-Weilburg is a rural district in the German state of Hesse, known for its historic town of Limburg an der Lahn and its location along the Lahn River.
-
C.
Bruchsal
Bruchsal is a town in the state of Baden-Württemberg in southwestern Germany, known for its baroque palace and asparagus cultivation.
-
D.
Fritzlar
Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
-
E.
Mainz-Kostheim
Mainz-Kostheim is a district of the city of Wiesbaden in Germany, located at the confluence of the Main and Rhine rivers opposite the city of Mainz.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b06c5d081909d31b8a537c94edb |
completed | May 3, 2026, 5:51 p.m. |
Created at: April 9, 2026, 9:52 p.m.