Triple
T4770977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Pinsker |
E105925
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pinsker |
E105925
|
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: Pinsker | Statement: [Leon Pinsker, familyName, Pinsker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pinsker Context triple: [Leon Pinsker, familyName, Pinsker]
-
A.
Pinsker
chosen
Pinsker is a Jewish surname most notably associated with Leo Pinsker, a 19th-century physician and early Zionist activist.
-
B.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
C.
Bryc
Bryc is an alternative spelling of the given name Bryce, typically used as a modern or stylistic variant.
-
D.
Parnes
Parnes is a mountain in Greece traditionally associated with the ancient Greek personifications of mountains known as the Ourea.
-
E.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a94e340819080fe92a2024abdaf |
completed | March 21, 2026, 6:28 a.m. |
Created at: March 20, 2026, 1:21 p.m.