Triple
T5816073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tola |
E128988
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Shamir |
E38677
|
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: Shamir | Statement: [Tola, burialPlace, Shamir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shamir Context triple: [Tola, burialPlace, Shamir]
-
A.
Shamir
Shamir is a Hebrew surname most prominently associated with Yitzhak Shamir, a former Prime Minister of Israel.
-
B.
Rabin
Rabin is a surname most prominently associated with Yitzhak Rabin, the Israeli military leader, statesman, and Nobel Peace Prize–winning prime minister.
-
C.
Merkle
Merkle is a surname most prominently associated with Ralph Merkle, a pioneering computer scientist and cryptographer known for his foundational work in public-key cryptography and Merkle trees.
-
D.
Pollard
Pollard is an English-language surname borne by various notable individuals across sports, politics, science, and the arts.
-
E.
Adi Shamir
chosen
Adi Shamir is an Israeli cryptographer best known as one of the co-inventors of the RSA public-key cryptosystem and a foundational figure in modern cryptography.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0336344148190bcf417c0b9617cb9 |
completed | March 22, 2026, 6:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c098504c68819089eff37ea1fa0979 |
completed | March 23, 2026, 1:33 a.m. |
Created at: March 22, 2026, 3:53 p.m.