Triple
T38130904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | רמת גן |
E952217
|
entity |
| Predicate | סוג רשות מקומית |
P108590
|
FINISHED |
| Object | עירייה |
—
|
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: עירייה | Statement: [רמת גן, סוג רשות מקומית, עירייה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: סוג רשות מקומית Context triple: [רמת גן, סוג רשות מקומית, עירייה]
-
A.
municipalOwnership
Indicates that an entity is owned, controlled, or held as property by a municipal (city or local) government.
-
B.
isPartOfMunicipalityType
chosen
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
C.
isMunicipalSectorOf
Indicates that one entity is a municipal-level subdivision, department, or sector that forms part of the organizational structure of another entity (typically a municipality or local government).
-
D.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
E.
municipalUse
Indicates that something is intended for, designated as, or used in connection with municipal or local government purposes.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.