Triple
T7004868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindauer |
E162426
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object | Lindauer (wine brand) |
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 (wine brand) | Statement: [Lindauer, hasNotableBearer, Lindauer (wine brand)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lindauer (wine brand) Context triple: [Lindauer, hasNotableBearer, Lindauer (wine brand)]
-
A.
Lindauer
chosen
Lindauer is a German surname borne by various notable individuals across fields such as science, art, and public life.
-
B.
Zisling
Zisling is a Hebrew-language surname most notably associated with Israeli politician and kibbutz movement leader Aharon Zisling.
-
C.
Winer
Winer is a surname most notably associated with Dave Winer, an influential software developer and pioneer of blogging and RSS technologies.
-
D.
Lauter
Lauter is a small river in Germany that serves as a tributary of the Innerste.
-
E.
Trimbach
Trimbach is a municipality in the canton of Solothurn in northwestern Switzerland.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc14037c81908bb87250ef29be50 |
completed | March 27, 2026, 7:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c76a3b2e9c8190b90c4eaaaea983ee |
completed | March 28, 2026, 5:42 a.m. |
Created at: March 27, 2026, 2:33 p.m.