Triple
T18912096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central District (Israel) |
E462632
|
entity |
| Predicate | hasRegionalCouncils |
P67101
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Central District (Israel), hasRegionalCouncils, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalCouncils Context triple: [Central District (Israel), hasRegionalCouncils, yes]
-
A.
containsRegionalCouncil
chosen
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
B.
hasRegionalGovernmentAbove
Indicates that one governmental unit is hierarchically subordinate to, and governed or overseen by, a higher-level regional government.
-
C.
hasProvincialCouncil
Indicates that an entity possesses or is governed by a provincial-level council as part of its administrative or organizational structure.
-
D.
numberOfRegionalCouncils
Indicates the total count of regional councils associated with a given entity.
-
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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c6238e288190b30311b5d80beafb |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.