Triple
T17306883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vezot Haberakhah |
E420185
|
entity |
| Predicate | mentionsTribe |
P831
|
FINISHED |
| Object | Zebulun |
E65912
|
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: Zebulun | Statement: [Vezot Haberakhah, mentionsTribe, Zebulun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zebulun Context triple: [Vezot Haberakhah, mentionsTribe, Zebulun]
-
A.
Zebulun
chosen
Zebulun is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Zebulun.
-
B.
Naphtali
Naphtali is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Naphtali.
-
C.
Issachar
Issachar is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Issachar.
-
D.
Zabulon
Zabulon is a variant form of the biblical given name Zebulun, traditionally associated with one of the twelve tribes of Israel.
-
E.
זְבֻלוּן
זְבֻלוּן הוא שם עברי מקראי, המזוהה בעיקר עם אחד משבטי ישראל ובנו של יעקב.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c440c58819084792fcd6b7a7a79 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:43 a.m.