Triple
T13609120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Wendt |
E325140
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wendt |
E811726
|
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: Wendt | Statement: [George Wendt, familyName, Wendt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wendt Context triple: [George Wendt, familyName, Wendt]
-
A.
Wendt
chosen
Wendt is a surname most notably associated with the German-born American landscape painter William Wendt, a key figure in early California Impressionism.
-
B.
Wendel
Wendel is a small unincorporated community located in rural northeastern California.
-
C.
Wende
Wende is a diminutive form of the given name Wendela, typically used as a familiar or affectionate variant.
-
D.
Wesselmann
Wesselmann is a surname most notably associated with Tom Wesselmann, a prominent American Pop Art painter known for his bold, stylized depictions of the nude and everyday consumer objects.
-
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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07f462c8190b5b5e115d550037f |
completed | April 12, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f98286c8190a866b5edc21f1225 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.