Triple
T13682023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לֵוִי |
E328025
|
entity |
| Predicate | halfSibling |
P363
|
FINISHED |
| Object | Benjamin |
E342186
|
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: Benjamin | Statement: [לֵוִי, halfSibling, Benjamin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Benjamin Context triple: [לֵוִי, halfSibling, Benjamin]
-
A.
Benjamin
Benjamin is the naive, dream-filled protagonist of Mendele Mocher Sforim’s satirical Yiddish novel "The Travels of Benjamin the Third," often likened to a Jewish Don Quixote.
-
B.
Benjamin
Benjamin is the full given name of the English playwright and poet Ben Jonson, a major literary figure of the early 17th century.
-
C.
Benjamin
Benjamin is the given first name of the American film producer and studio executive B. P. Schulberg.
-
D.
Benjamin
Benjamin is the given name of Benjamin Breckinridge Warfield, a prominent American Presbyterian theologian and professor at Princeton Theological Seminary in the late 19th and early 20th centuries.
-
E.
Benjamin
chosen
Benjamin is a masculine given name of Hebrew origin meaning "son of the right hand" or "favored son," widely used in many cultures and 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7944551b481909833cdcff198889c |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:53 p.m.