Triple
T11591887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennie Niehaus |
E274901
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Niehaus |
E662418
|
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: Niehaus | Statement: [Lennie Niehaus, familyName, Niehaus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niehaus Context triple: [Lennie Niehaus, familyName, Niehaus]
-
A.
Niehaus
chosen
Niehaus is a surname of German origin borne by various notable individuals across fields such as sports, broadcasting, and academia.
-
B.
Neuhaus
Neuhaus is a locality within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
-
C.
Naast
Naast is a village in the Walloon region of Belgium that forms part of the municipality of Soignies in the province of Hainaut.
-
D.
Nyhausen
Nyhausen is a locality in Germany historically noted as the birthplace of the Swedish nobleman and soldier Philip Christoph von Königsmarck.
-
E.
Niehove
Niehove is a historic terp village in the Dutch province of Groningen, known for its distinctive radial layout and well-preserved traditional architecture.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946594348190935106132fd18028 |
completed | April 10, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e714634b308190bdcb761f8b6712e7 |
completed | April 21, 2026, 6:08 a.m. |
Created at: April 8, 2026, 9:38 p.m.