Triple
T18561664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy Wiebe |
E453654
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wiebe |
—
|
NE NERFINISHED |
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: Wiebe | Statement: [Rudy Wiebe, familyName, Wiebe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wiebe Context triple: [Rudy Wiebe, familyName, Wiebe]
-
A.
Wiebe
chosen
Wiebe is a given name and surname of Frisian and Dutch origin, used in various forms across the Netherlands and surrounding regions.
-
B.
Wieber
Wieber is the surname of American artistic gymnast Jordyn Wieber, a 2012 Olympic gold medalist and 2011 world all-around champion.
-
C.
Schmarbeck
Schmarbeck is a small watercourse in Lower Saxony, Germany, known as one of the minor streams feeding into the Örtze River within the Lüneburg Heath region.
-
D.
Schmarbeck
Schmarbeck is a small village in Lower Saxony, Germany, that forms part of the collective municipality of Faßberg.
-
E.
Weitzel
Weitzel is a surname of likely German or Dutch origin borne by individuals such as Edu Weitzel Douwes Dekker.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5380a46f08190afe7ca2ddfe209d5 |
completed | April 19, 2026, 8:16 p.m. |
Created at: April 10, 2026, 11:42 a.m.