Triple
T11604081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beryl David Rosofsky |
E275207
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Rosofsky |
E157984
|
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: Rosofsky | Statement: [Beryl David Rosofsky, familyName, Rosofsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rosofsky Context triple: [Beryl David Rosofsky, familyName, Rosofsky]
-
A.
Rosofsky
chosen
Rosofsky is a Jewish surname associated with individuals such as the American boxer and war hero Barney Ross, whose birth name was Barnet David Rosofsky.
-
B.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
C.
Rosenfeld
Rosenfeld is a notable architectural work designed by 19th-century American architect Alexander Jackson Davis.
-
D.
Rothkowitz
Rothkowitz is the original family surname of the abstract expressionist painter Mark Rothko, reflecting his Eastern European Jewish heritage.
-
E.
Rosenstein
Rosenstein is a surname most notably associated with Justin Rosenstein, the American software programmer and co-founder of Asana.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d895502e0081909ee9c3d45d26cd91 |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a8022800819096d7a87ac8c1c751 |
completed | April 22, 2026, 10:50 a.m. |
Created at: April 8, 2026, 9:38 p.m.