Triple
T16719019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon ben Boethus |
E406296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Second Temple period person |
C29903
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Second Temple period person Context triple: [Simon ben Boethus, instanceOf, Second Temple period person]
-
A.
1st-century Jew
A 1st-century Jew is an individual living in the lands of Judea and the broader Roman Empire during the first century CE who identifies with the Jewish people through ancestry, adherence to Jewish religious practices, and participation in the social, cultural, and legal traditions rooted in the Hebrew Scriptures and Second Temple Judaism.
-
B.
Babylonian Jew
A Babylonian Jew is a member of the Jewish community historically rooted in Babylonia (primarily in present-day Iraq), whose religious, cultural, and intellectual life was shaped by centuries of diaspora experience and the development of major Jewish texts such as the Babylonian Talmud.
-
C.
Jewish priest
chosen
A Jewish priest (Kohen) is a male descendant of Aaron who holds hereditary ritual and liturgical responsibilities within the Jewish religious tradition.
-
D.
Judean official
A Judean official is a governmental or administrative authority from ancient Judea responsible for overseeing civic, legal, or religious affairs within the region.
-
E.
1st-century BCE person
A 1st-century BCE person is an individual who lived during the period from 100 BCE to 1 BCE, shaped by the political, cultural, and social contexts of the late ancient world.
- F. None of above.
Provenance (1 batch)
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.