Triple
T4084281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yohanan Bader |
E87551
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bader |
E10528
|
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: Bader | Statement: [Yohanan Bader, familyName, Bader]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bader Context triple: [Yohanan Bader, familyName, Bader]
-
A.
Bader
chosen
Bader is the maiden surname of Ruth Bader Ginsburg, the late U.S. Supreme Court Justice and pioneering advocate for gender equality.
-
B.
Trevour
Trevour is a less common variant spelling of the given name Trevor, typically used as a masculine first name.
-
C.
Butrus
Butrus is an alternative transliteration of the Arabic given name "Boutros," itself derived from "Peter."
-
D.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
E.
Eberhardt
Eberhardt is a German masculine given name and surname derived from Old High German elements meaning "boar" and "brave" or "hardy."
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7a4b488190ab466e2c50329ab3 |
completed | March 9, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562c9760c8190a9292eb1cea55ab2 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.