Triple
T9180795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freudenstadt |
E220321
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Nagold |
E95811
|
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: Nagold | Statement: [Freudenstadt, locatedNear, Nagold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagold Context triple: [Freudenstadt, locatedNear, Nagold]
-
A.
Nagold
chosen
Nagold is a river in southwestern Germany that flows through the Black Forest region before joining the Enz River.
-
B.
Reichenau
Reichenau is a German municipality best known for its UNESCO-listed monastic island on Lake Constance, renowned for its medieval abbey and cultural heritage.
-
C.
Pfinz
Pfinz is a river in Baden-Württemberg, Germany, that flows through the northern Black Forest region and the Karlsruhe area before joining the Enz.
-
D.
Seebruck
Seebruck is a Bavarian lakeside village and popular holiday resort on the northern shore of Lake Chiemsee in southern Germany.
-
E.
Traun
Traun is a town in the Austrian state of Upper Austria, located near Linz along the Traun River and known as a residential and industrial suburb of the regional capital.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc251da448190a5c7f684dac15a84 |
completed | April 1, 2026, 6:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d054b5512c8190aa7909ef8b56b186 |
completed | April 4, 2026, midnight |
Created at: March 30, 2026, 7:23 p.m.