Triple
T2964106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel |
E80119
|
entity |
| Predicate | hasChild |
P369
|
FINISHED |
| Object | Naphtali |
E65104
|
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: Naphtali | Statement: [Israel, hasChild, Naphtali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Naphtali Context triple: [Israel, hasChild, Naphtali]
-
A.
Naphtali
chosen
Naphtali is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Naphtali.
-
B.
Issachar
Issachar is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Issachar.
-
C.
Zebulun
Zebulun is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Zebulun.
-
D.
Yosef
Yosef is a Hebrew given name of biblical origin, best known from the patriarch Joseph and widely used in Jewish communities.
-
E.
Or Yehuda
Or Yehuda is a city in central Israel, located in the Tel Aviv District and functioning largely as a residential suburb of the Tel Aviv metropolitan area.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9958b1e48190a77f37bf63333c5b |
completed | March 8, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fc98d94481908282d21394dc24a7 |
completed | March 11, 2026, 5:24 a.m. |
Created at: March 8, 2026, 2:58 p.m.