Triple
T10869640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justus Jonas |
E256616
|
entity |
| Predicate | workLocation |
P7
|
FINISHED |
| Object | Eisfeld |
E919533
|
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: Eisfeld | Statement: [Justus Jonas, workLocation, Eisfeld]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eisfeld Context triple: [Justus Jonas, workLocation, Eisfeld]
-
A.
Eisfeld
chosen
Eisfeld is a small town in the Thuringia region of central Germany, known for its historical architecture and location along the Werra River.
-
B.
Feldbach
Feldbach is a small town in southeastern Austria known for its historic center and location in the Styrian volcanic region.
-
C.
Niederfeld
Niederfeld is a district within the Mannheim borough of Neckarau in the German state of Baden-Württemberg.
-
D.
Ochsenfeld
Ochsenfeld is a German surname most notably borne by physicist Robert Ochsenfeld, known for his work on superconductivity.
-
E.
Hellefeld
Hellefeld is a village and district within the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75170665881909944f92c2cdbe7e6 |
completed | April 9, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b76fa8348190bb42f1c71eb0e545 |
completed | April 20, 2026, 5:19 a.m. |
Created at: April 8, 2026, 9:20 p.m.