Triple
T9662647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachish |
E233624
|
entity |
| Predicate | culture |
P1114
|
FINISHED |
| Object | Judahite |
E83090
|
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: Judahite | Statement: [Lachish, culture, Judahite]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Judahite Context triple: [Lachish, culture, Judahite]
-
A.
Judah
Judah was an ancient Israelite kingdom in the southern Levant, centered around Jerusalem and prominent in biblical history.
-
B.
Israelites
chosen
The Israelites are the ancient Hebrew people who trace their origins to the patriarchs of the Hebrew Bible and became the foundational ethnic and religious community of Judaism.
-
C.
Edomite
Edomite was an extinct Northwest Semitic language once spoken by the ancient Edomites in the region south of the Kingdom of Judah.
-
D.
יהודה
יהודה הוא אחד מבני יעקב, שממנו יצאה שבט יהודה המרכזי בעם ישראל והמסורת מייחסת לו תפקיד חשוב בהתפתחות ההנהגה והמלכות בישראל.
-
E.
Yehuda
Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a1422348190967943b0d4da8efd |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:14 p.m.