Triple
T19326158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eselsburger Tal |
E483359
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object |
Eselsburg
Eselsburg is a small village in southern Germany, known for its picturesque setting in the Swabian Jura near the scenic Eselsburger Valley.
|
E1370569
|
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: Eselsburg | Statement: [Eselsburger Tal, locatedNear, Eselsburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eselsburg Context triple: [Eselsburger Tal, locatedNear, Eselsburg]
-
A.
Sporenburg
Sporenburg is a residential peninsula in Amsterdam known for its modern architecture and innovative urban design within the city’s Eastern Docklands.
-
B.
Sporenburg
Sporenburg is a small island located adjacent to Borneo Island.
-
C.
Doesburg
Doesburg is a historic city in the Dutch province of Gelderland, known for its well-preserved medieval center and location at the confluence of the IJssel and Oude IJssel rivers.
-
D.
Spakenburg
Spakenburg is a historic fishing village in the Dutch province of Utrecht, known for its traditional wooden boats, preserved harbor, and distinctive local costumes.
-
E.
Eelde
Eelde is a village in the Dutch province of Drenthe, known for its proximity to Groningen Airport Eelde and its historic annual flower parade.
- 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: Eselsburg Triple: [Eselsburger Tal, locatedNear, Eselsburg]
Generated description
Eselsburg is a small village in southern Germany, known for its picturesque setting in the Swabian Jura near the scenic Eselsburger Valley.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Eselsburg Target entity description: Eselsburg is a small village in southern Germany, known for its picturesque setting in the Swabian Jura near the scenic Eselsburger Valley.
-
A.
Sporenburg
Sporenburg is a residential peninsula in Amsterdam known for its modern architecture and innovative urban design within the city’s Eastern Docklands.
-
B.
Sporenburg
Sporenburg is a small island located adjacent to Borneo Island.
-
C.
Doesburg
Doesburg is a historic city in the Dutch province of Gelderland, known for its well-preserved medieval center and location at the confluence of the IJssel and Oude IJssel rivers.
-
D.
Spakenburg
Spakenburg is a historic fishing village in the Dutch province of Utrecht, known for its traditional wooden boats, preserved harbor, and distinctive local costumes.
-
E.
Eelde
Eelde is a village in the Dutch province of Drenthe, known for its proximity to Groningen Airport Eelde and its historic annual flower parade.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8bb28c81909b3a3bbb96b69b4f |
completed | April 20, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a071bdc5a2881908b7e71c397be2c2f |
completed | May 15, 2026, 1:13 p.m. |
| NEDg | Description generation | batch_6a071ca19f308190ac9072c5a8d3b665 |
completed | May 15, 2026, 1:16 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a071de35b9081908d1b6e797cbe69ce |
completed | May 15, 2026, 1:21 p.m. |
Created at: April 10, 2026, 1:33 p.m.