Triple
T15836788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gershom |
E384004
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Eliezer |
E971803
|
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: Eliezer | Statement: [Gershom, sibling, Eliezer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eliezer Context triple: [Gershom, sibling, Eliezer]
-
A.
Eliezer
chosen
Eliezer is the son of Moses mentioned in the Hebrew Bible, whose name reflects Moses’ gratitude for God’s help and deliverance.
-
B.
Eliezer
Eliezer is the Hebrew given name of Elie Wiesel, the Holocaust survivor, author, and Nobel Peace Prize laureate.
-
C.
Yosef
Yosef is a Hebrew given name of biblical origin, best known from the patriarch Joseph and widely used in Jewish communities.
-
D.
Noam Elimelech
Noam Elimelech is a foundational Hasidic work of mystical and ethical teachings by Rabbi Elimelech of Lizhensk, highly influential in shaping early Hasidic thought and spirituality.
-
E.
Yosefa
Yosefa is a feminine given name of Hebrew origin, commonly used in Jewish communities.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e1fcd48190bcb884f6c65db847 |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa13a83448190adcad8bb84622e55 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 4:49 a.m.