Triple
T2165097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Wigand |
E46890
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wigand |
E240663
|
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: Wigand | Statement: [Johann Wigand, familyName, Wigand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wigand Context triple: [Johann Wigand, familyName, Wigand]
-
A.
Wigand
Wigand is a surname most notably associated with Jeffrey Wigand, the American whistleblower who exposed the tobacco industry's knowledge of the dangers of smoking.
-
B.
Otto Wigand
Otto Wigand was a 19th-century German publisher known for issuing influential socialist and political works, including early editions of Friedrich Engels’ writings.
-
C.
Johann Wigand
chosen
Johann Wigand was a 16th-century German Lutheran theologian and bishop known for his role in the Protestant Reformation and his writings defending Lutheran doctrine.
-
D.
Wolff
Wolff is a German surname borne by numerous notable individuals across fields such as philosophy, science, and the arts.
-
E.
Wirth
Wirth is a Swiss surname most notably associated with computer scientist Niklaus Wirth, the designer of several influential programming languages.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8e1cfc81908adc0357ddfec701 |
completed | March 7, 2026, 5:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5d98286c8190a6890e2c7daa10b5 |
completed | March 9, 2026, 5:41 a.m. |
Created at: March 4, 2026, 7:45 p.m.