Triple
T20029591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf Joffe |
E495084
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Joffe |
—
|
NE NERFINISHED |
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: Joffe | Statement: [Adolf Joffe, familyName, Joffe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joffe Context triple: [Adolf Joffe, familyName, Joffe]
-
A.
Joffe
chosen
Joffe is a surname most notably associated with Adolf Joffe, a prominent early 20th-century Russian revolutionary and diplomat.
-
B.
Ravnitzky
Ravnitzky is a Jewish family name most notably associated with Yehoshua Ravnitzky, a prominent Hebrew writer, editor, and publisher.
-
C.
Ghirshman
Ghirshman is the surname of Roman Ghirshman, a prominent 20th-century French archaeologist known for his influential work on ancient Iran and the Near East.
-
D.
Ossip
Ossip is a masculine given name of Slavic origin, notably borne by pianist and conductor Ossip Gabrilowitsch.
-
E.
Ussishkin
Ussishkin is a Jewish family name most prominently associated with Zionist leader Menachem Ussishkin.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662908df081909a6c8ccf0dd90fff |
completed | April 20, 2026, 5:29 p.m. |
Created at: April 11, 2026, 3:36 p.m.