Triple
T3649854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph |
E77392
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Yosef |
E137757
|
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: Yosef | Statement: [Joseph, hasVariant, Yosef]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yosef Context triple: [Joseph, hasVariant, Yosef]
-
A.
Yosef
chosen
Yosef is a Hebrew given name of biblical origin, best known from the patriarch Joseph and widely used in Jewish communities.
-
B.
Reuven
Reuven is a Hebrew given name commonly used for males, notably borne by Israeli politician and former president Reuven Rivlin.
-
C.
Shlomo
Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
-
D.
Yehuda
Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
-
E.
Menachem
Menachem is a Hebrew given name commonly associated with Jewish men, notably borne by figures such as Israeli Prime Minister Menachem Begin.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38fa1988190b630329700afc3dd |
completed | March 8, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4c38f989c8190befc64db51041a53 |
completed | March 14, 2026, 2:10 a.m. |
Created at: March 8, 2026, 3:24 p.m.