Triple
T13672893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse |
E327795
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Yishai |
E187954
|
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: Yishai | Statement: [Jesse, hasVariant, Yishai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yishai Context triple: [Jesse, hasVariant, Yishai]
-
A.
Yishai
chosen
Yishai is the Hebrew form of the biblical name Jesse, known as the father of King David in the Hebrew Bible.
-
B.
Tzippori
Tzippori is an archaeological site and modern village in Israel known for its rich remains from the Roman and Byzantine periods, including impressive mosaics and ancient Jewish and early Christian heritage.
-
C.
Yakir
Yakir is a masculine given name of Hebrew origin, commonly used in Israel and among Jewish communities.
-
D.
Rehavia
Rehavia is a historic, centrally located Jerusalem neighborhood known for its leafy streets, Bauhaus-style architecture, and mix of intellectual, political, and cultural residents.
-
E.
Eyal
Eyal is a masculine given name of Hebrew origin, commonly used in Israel.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65aab348190a6611f5765f8392d |
completed | April 12, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b1222648190a70f50e6e5c34593 |
completed | May 3, 2026, 5:51 p.m. |
Created at: April 9, 2026, 9:53 p.m.