Triple
T6800670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindau |
E156177
|
entity |
| Predicate | demonym |
P191
|
FINISHED |
| Object | Lindauer |
E162426
|
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: Lindauer | Statement: [Lindau, demonym, Lindauer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lindauer Context triple: [Lindau, demonym, Lindauer]
-
A.
Lindauer
chosen
Lindauer is a German surname borne by various notable individuals across fields such as science, art, and public life.
-
B.
Röthlein
Röthlein is a small municipality in the Schweinfurt district of Bavaria, Germany.
-
C.
Brackenberg
Brackenberg is an early recorded historical name for the Brocken, the highest peak in Germany’s Harz Mountains.
-
D.
Lauterach
Lauterach is a small municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, known for its rural character and scenic Swabian Jura surroundings.
-
E.
Luterbach
Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e457408190a0ad9b0c48d8147c |
completed | March 27, 2026, 6:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a9b0cc48190819380aeaf0228e7 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:15 p.m.