Triple
T9748110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shmuel Sambursky |
E236368
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Shmuel |
E113393
|
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: Shmuel | Statement: [Shmuel Sambursky, givenName, Shmuel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shmuel Context triple: [Shmuel Sambursky, givenName, Shmuel]
-
A.
Shmuel
chosen
Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
-
B.
Shlomo
Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
-
C.
Shlomtzion
Shlomtzion is the Hebrew name of Salome Alexandra, a 1st-century BCE Hasmonean queen of Judea known for her pious rule and support of the Pharisees.
-
D.
Benzion
Benzion is a Hebrew masculine given name meaning "son of Zion," traditionally used in Jewish communities.
-
E.
Eleazar
Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f68f8b88190b44babf5ae17dfef |
completed | April 1, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1b00d76488190af68cba694dc329c |
completed | April 5, 2026, 12:42 a.m. |
Created at: March 30, 2026, 8:23 p.m.