Triple
T4954256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahlon |
E111242
|
entity |
| Predicate | fromRegion |
P410
|
FINISHED |
| Object | Judah |
E476638
|
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: Judah | Statement: [Mahlon, fromRegion, Judah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Judah Context triple: [Mahlon, fromRegion, Judah]
-
A.
Judah
chosen
Judah was an ancient Israelite kingdom in the southern Levant, centered around Jerusalem and prominent in biblical history.
-
B.
Yehuda
Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
-
C.
Naphtali
Naphtali is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Naphtali.
-
D.
Binyamin
Binyamin is a figure in Islamic and biblical tradition known as the younger brother of the prophet Yusuf (Joseph).
-
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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b945c0819082723712905f8295 |
completed | March 20, 2026, 4:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81da92b48190ab41ad8f7a891544 |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:32 p.m.