Triple
T8526794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern District, Israel |
E201837
|
entity |
| Predicate | containsRegionalCouncils |
P67101
|
FINISHED |
| Object | multiple regional councils |
—
|
LITERAL 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: multiple regional councils | Statement: [Southern District, Israel, containsRegionalCouncils, multiple regional councils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRegionalCouncils Context triple: [Southern District, Israel, containsRegionalCouncils, multiple regional councils]
-
A.
containsRegionalCouncil
chosen
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
B.
numberOfRegionalCouncils
Indicates the total count of regional councils associated with a given entity.
-
C.
hasRegionalDevelopmentBoard
Indicates that an entity is associated with or overseen by a specific regional development board.
-
D.
seatOfRegionalCouncil
Indicates that a location serves as the administrative center or headquarters of a regional council.
-
E.
hasRegionalCommission
Indicates that an entity is associated with, overseen by, or falls under the jurisdiction of a specific regional commission.
- F. None of above.
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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6477100819081fa20cb6b8ea3d7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.