Triple
T22356722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehovot Subdistrict |
E552672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdistrict of Israel |
C46151
|
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: subdistrict of Israel Context triple: [Rehovot Subdistrict, instanceOf, subdistrict of Israel]
-
A.
administrative district of Israel
An administrative district of Israel is a primary territorial division used by the Israeli government to organize local governance, public administration, and the delivery of state services.
-
B.
populated place in Israel
A populated place in Israel is a geographically defined area within the State of Israel where people live, such as a city, town, village, kibbutz, or moshav, recognized for administrative, residential, or communal purposes.
-
C.
Israeli settlement region
An Israeli settlement region is a geographically defined area in territories occupied by Israel where Israeli civilian communities are established and administered under Israeli authority, often amid international dispute and complex legal and political status.
-
D.
Jerusalem neighborhood
A Jerusalem neighborhood is a distinct urban area within the city of Jerusalem characterized by its unique historical, cultural, religious, and architectural identity, as well as its local community and services.
-
E.
Israeli local council
An Israeli local council is a type of municipal government in Israel that administers and provides local services to a medium-sized community that is not large enough to be designated as a city.
- F. None of above. chosen
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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.