Triple
T17493418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirschhorn am Neckar |
E425985
|
entity |
| Predicate | locatedWestOf |
P4239
|
FINISHED |
| Object | Eberbach (Baden) |
—
|
NE NERFINISHED |
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: Eberbach (Baden) | Statement: [Hirschhorn am Neckar, locatedWestOf, Eberbach (Baden)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eberbach (Baden) Context triple: [Hirschhorn am Neckar, locatedWestOf, Eberbach (Baden)]
-
A.
Eberbach
chosen
Eberbach is a small historic town in southwestern Germany, known for its picturesque location in the Odenwald hills along the Neckar River.
-
B.
Erbach (Bad Camberg)
Erbach is a district of the spa town Bad Camberg in Hesse, Germany, characterized by its residential areas and local rural surroundings.
-
C.
Erbach-Fürstenau
Erbach-Fürstenau is a locality historically associated with the former County of Erbach in what is now the German state of Hesse.
-
D.
Erbach-Schönberg
Erbach-Schönberg was a mediatized German noble line and territory associated with the House of Erbach in the historic region of Hesse.
-
E.
Emsbach
Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d6bd548190b4c6fae27c2a9ae8 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:48 a.m.