Triple
T7853302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Rosebanks Shulman |
E182108
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Shulman |
E146154
|
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: Shulman | Statement: [Jonathan Rosebanks Shulman, familyName, Shulman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shulman Context triple: [Jonathan Rosebanks Shulman, familyName, Shulman]
-
A.
Shulman
chosen
Shulman is a surname of Jewish origin borne by various notable individuals in fields such as literature, academia, and the arts.
-
B.
Shapiro
Shapiro is a surname of Jewish origin commonly borne by individuals of Ashkenazi descent.
-
C.
Salzman
Salzman is the surname of Linda Salzman Sagan, an American artist and writer known for co-designing the Pioneer plaque sent into space.
-
D.
Shulmanov
Shulmanov is a Slavic patronymic surname derived from the Jewish surname Shulman, typically meaning "son of Shulman."
-
E.
Rosenblum
Rosenblum is a Jewish surname borne by various notable individuals, including Israeli journalist and politician Herzl Rosenblum.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ed56d481909266d862e0ae152d |
completed | March 31, 2026, 12:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b1e9e808190a0eb2dea5288e743 |
completed | March 31, 2026, 5:26 a.m. |
Created at: March 30, 2026, 4:51 p.m.