Triple
T16850501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutterberg |
E409660
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Lutterberg (German) |
E409660
|
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: Lutterberg (German) | Statement: [Lutterberg, hasNameInLanguage, Lutterberg (German)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lutterberg (German) Context triple: [Lutterberg, hasNameInLanguage, Lutterberg (German)]
-
A.
Lutterberg
chosen
Lutterberg is a village in Lower Saxony, Germany, historically notable as the site of the 1758 Battle of Lutterberg during the Seven Years' War.
-
B.
Leuenberg
Leuenberg is a village in Switzerland known as the site where major European Protestant churches concluded the Leuenberg Agreement on church fellowship.
-
C.
Lutter (Örtze)
Lutter (Örtze) is a small river in Lower Saxony, Germany, that forms part of the Örtze river system.
-
D.
Lunzenau
Lunzenau is a small town in the German state of Saxony, known for its location along the Zwickauer Mulde river and its historic architecture.
-
E.
Landensberg
Landensberg is a small municipality in the Bavarian region of southern 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b378dda48190ab81d75f2cfe3ab3 |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb1f02648190937c692af83843dc |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.