Triple
T12839430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirley N. Weber |
E307007
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Weber |
E154323
|
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: Weber | Statement: [Shirley N. Weber, familyName, Weber]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weber Context triple: [Shirley N. Weber, familyName, Weber]
-
A.
Weber
chosen
Weber is a common German surname borne by numerous notable individuals across fields such as sociology, music, and politics.
-
B.
Weinert
Weinert is a German-language surname borne by various notable individuals in fields such as the arts, sciences, and public life.
-
C.
Weihmichl
Weihmichl is a small municipality in Lower Bavaria, Germany, known for its rural character and proximity to the city of Landshut.
-
D.
Seelbach
Seelbach is a municipality in southwestern Germany’s Baden-Württemberg region, situated in the Ortenau district near the Black Forest.
-
E.
Wiebe
Wiebe is a given name and surname of Frisian and Dutch origin, used in various forms across the Netherlands and surrounding regions.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff11b4481909fb2f92c46186853 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68edd30e881909062e8f91f614990 |
completed | May 2, 2026, 11:55 p.m. |
Created at: April 9, 2026, 5:35 p.m.