Triple
T8526754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern District, Israel |
E201837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of Israel |
C24011
|
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: administrative district of Israel Context triple: [Southern District, Israel, instanceOf, administrative district of Israel]
-
A.
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.
-
B.
Palestinian territory
Palestinian territory refers to the geographic areas of the West Bank, including East Jerusalem, and the Gaza Strip that are claimed by Palestinians for a future independent state and are subject to ongoing political and territorial disputes.
-
C.
Rishon
A Rishon is a hypothetical fundamental constituent of matter proposed in preon models, envisioned as a more elementary particle from which quarks and leptons are composed.
-
D.
Israel–Jordan institution
An Israel–Jordan institution is an organization, body, or framework jointly established or formally recognized by both Israel and Jordan to manage, coordinate, or promote cooperation in areas such as security, water resources, trade, or diplomacy.
-
E.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:16 p.m.