Triple
T20251175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro |
E498558
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Szapiro |
E498558
|
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: Szapiro | Statement: [Shapiro, hasVariant, Szapiro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Szapiro Context triple: [Shapiro, hasVariant, Szapiro]
-
A.
Shapiro
chosen
Shapiro is a surname of Jewish origin commonly borne by individuals of Ashkenazi descent.
-
B.
Szpiner
Szpiner is a French surname most notably borne by Francis Szpiner, a prominent lawyer and political figure in France.
-
C.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
D.
Sprinzak
Sprinzak is a Hebrew surname most notably associated with Yosef Sprinzak, an early Israeli politician and the first Speaker of the Knesset.
-
E.
Spychalski
Spychalski is a Polish surname borne by various individuals, including notable figures in Poland’s political and military history.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a8b8488190b344df7a65f59684 |
completed | April 20, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0855262c548190b5f6102b4e6e01a6 |
completed | May 16, 2026, 11:29 a.m. |
Created at: April 11, 2026, 11:41 p.m.